[GRADLE-3508] UP-TO-DATE check ignores changes in the order of files on Java compile classpath Created: 20/Jul/16 Updated: 21/Jul/16 Resolved: 21/Jul/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | 3.1-rc-1 |
| Type: | Bug | ||
| Reporter: | Lóránt Pintér | Assignee: | Lóránt Pintér |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
Steps to reproduce: 1) run a build with a build.gradle like this:
task compile(type: JavaCompile) {
sourceCompatibility = JavaVersion.current()
targetCompatibility = JavaVersion.current()
destinationDir = file("build/classes")
dependencyCacheDir = file("build/dependency-cache")
source "src/main/java"
classpath = files('lib1.jar', 'lib2.jar')
}
2) then run the same build but with the classpath order reversed:
classpath = files('lib2.jar', 'lib1.jar')
The compile task is UP-TO-DATE but it shouldn't be. |
| Comments |
| Comment by Lóránt Pintér [ 21/Jul/16 ] |
|
Properties can now be annotated with @OrderSensitive to turn on checking for changes in file order. |