Comments (6)
up-to-date checks of compileGwt work for me. On the second run it's correctly marked as UP-TO-DATE. I tested it using one of the example projects and a real world project. The output of the example project's build:
[sts] -----------------------------------------------------
[sts] Starting Gradle build for the following tasks:
[sts] :example-simple-war:assemble
[sts] -----------------------------------------------------
The TaskContainer.add() method has been deprecated and is scheduled to be removed in Gradle 2.0. Please use the create() method instead.
:example-simple-war:compileJava UP-TO-DATE
:example-simple-war:processResources UP-TO-DATE
:example-simple-war:classes UP-TO-DATE
:example-simple-war:compileGwt UP-TO-DATE
:example-simple-war:war UP-TO-DATE
:example-simple-war:assemble UP-TO-DATE
BUILD SUCCESSFUL
Total time: 2.25 secs
[sts] -----------------------------------------------------
[sts] Build finished succesfully!
[sts] Time taken: 0 min, 2 sec
[sts] -----------------------------------------------------
So I guess it is related to your specific build. Be aware that not only the source files are relevant for the up-to-date check but also the compiler flags that possibly change the output (e.g. turning closure compiler on/off).
As far as I remember appending "-i" (sets the log level to info) to the gradle command line will show why the task isn't considered up-to-date.
I'll leave this issue open to wait for feedback. Possibly it's an issue that only occurs in a specific configuration.
from gwt-gradle-plugin.
OK, I tested it some more.
The up-to-date check works fine but when I add style = 'DETAILED' the check is broken in our build. I can't get this reproduced in the the example project simple-war.
Output from gradle :compileGwt -i in our build is always although the style never changes:
Executing task ':compileGwt' (up-to-date check took 0.069 secs) due to:
Value of input property 'style' has changed for task ':compileGwt'
from gwt-gradle-plugin.
This seems to be a class loader problem or alike. After debugging gradle I can see that the current style value, when compared with the value from the previous run, is in fact two different instances of the same enum value.
object1 Style (id=7033)
'object1' referenced from:
name "OBF" (id=217)
ordinal 0 [0x0] [^@ (NUL)]
object2 Style (id=6977)
'object2' referenced from:
name "OBF" (id=217)
ordinal 0 [0x0] [^@ (NUL)]
from gwt-gradle-plugin.
The track at gradle.org ...
http://issues.gradle.org/browse/GRADLE-3018
from gwt-gradle-plugin.
+1 sounds like #77 is a duplicate of this
from gwt-gradle-plugin.
@rbaradari I'm investigating Gradle's handling of UP-TO-DATE
checking when using enum
properties as @Inputs
. Indeed what's happening is that Gradle creates a new ClassLoader
under certain circumstances (for example, if the build.gradle
is changed) and since we're comparing instances of Style
etc. from different ClassLoaders, they're not equal.
However, I'm having trouble reproducing the specific behavior you're seeing. I have created an example GWT project in the hopes of replicating this exact behavior.
It would be especially helpful if you could answer 2 things for me:
- Are you using the Gradle Daemon?
- Do you have any example project that you can share that exhibits the behavior you describe in this issue? If not, can you tell me what types of changes you're making and what Gradle tasks you're executing?
from gwt-gradle-plugin.
Related Issues (20)
- [gwt 2.7.0/gradle 2.12./plug-in 0.6] gwtSuperDev - java.lang.OutOfMemoryError HOT 8
- [GWT 2.8/Pluging 0.6] Issue with gwt sub-projects HOT 1
- [GWT 2.8-SNAPSHOT/Gradle 2.13] Properties issue HOT 5
- Make gwt-unitcache and war directories configurable
- gwt + gradle + lombok issues resolved
- Have any way to generate i18n and generateAsync supported by gwt-maven-plugin? HOT 6
- vaadinCompile issue, with vaadin 8 at 1.0 version
- compileGwt is missing module descriptor of a submodule on classpath HOT 8
- Make the compile tasks cacheable
- Missing support for Gradle Composite Builds
- Gradle ... single directory for all classes .. is scheduled to be removed in Gradle 5.0 HOT 1
- gwt-gradle-plugin uses deprecated api by Gradle 4.0 HOT 3
- Updated GPE Changes Property Variables
- GenerateGdt Task Needs To Also Be a Dependency of eclipseWtp
- Gradle upgrade to 5.4 causes build failure HOT 3
- CreateProcess error=206, The filename or extension is too long HOT 1
- Buildship Support HOT 1
- Has this plug-in been tested with GWT 2.8.Beta? HOT 2
- Integreation with Gretty plugin
- example build failed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gwt-gradle-plugin.