Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

Change in pure Java dependency does not cause GWT project to recompile #88

Open
dhoskins opened this issue Jul 22, 2015 · 1 comment
Open

Comments

@dhoskins
Copy link

I have a project with two subprojects: GWT and Core. Core is a pure Java project which GWT relies upon. The GWT build.gradle looks like this:

apply plugin: 'gwt-compiler'
buildscript {
    repositories {
        jcenter() //repository where to fetch gwt gradle plugin
    }

    dependencies {
        classpath 'de.richsource.gradle.plugins:gwt-gradle-plugin:0.6'
    }
}

dependencies {
    compile project(':core')
    ... other dependencies ....
}

gwt {
    modules <myModuleName>
}

This builds fine, however does not recompile when I make a change to the Core project. The core jar rebuilds as expected, the GWT tasks all report "UP-TO-DATE".

I have tried adding src += files(project(':core').sourceSets.main.allJava.srcDirs) to the gwt component but this does not help either.

@flegall
Copy link

flegall commented Mar 11, 2016

Same bug here.

I have used the following workaround:
compileGwt.inputs.files(tasks.getByPath(":core:jar").outputs.files.getAsPath())
Basically, it adds the core jar as an input file dependency, this way, when a file in "core" is updated, the compileGwt recompiles afterwards.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants