[GRADLE-3431] Gradle should warn user given sourceSets and source trees that don't match Created: 07/Apr/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.12
Fix Version/s: None

Type: Bug
Reporter: Eric Wendelin Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: File SimpleIncrementalIssue.jar    
Issue Links:
Related to GRADLE-3428 Incremental Java compilation changing... Resolved


Given the following inconsistent file structure and build.gradle file, the vast majority of Gradle build features work but some do not. We should warn users when we encounter this scenario to avoid confusion or unnecessarily broken builds.

File tree

├── build.gradle
└── src
├── java
│ └── java (<--- extra java/ directory here)
│ └── com
│ └── google
│ └── jedo
│ └── IncDep
│ └── DepTwo.java
├── main
│ └── java
│ └── com
│ └── google
│ └── jedo
│ └── IncrementalJava
│ ├── DepOne.java
│ └── Main.java


apply plugin: ‘java’
sourceSets {
main {

{ srcDir 'src/java' srcDir 'src/main/java' }


{ //enable incremental compilation options.incremental = true }

From Gary:

When you specify the "-d" option to the java compiler (destination directory) it derives the location of the class files from the package of the class and not the path of the source file. For example, if I run `javac java/com/google/jedo/IncDep/DepTwo.java`, it puts the class file in the same directory as the source file. On the other hand, if I say `javac -d /tmp java/com/google/jedo/IncDep/DepTwo.java` it creates the directory structure based on the package and drops the class in /tmp/com/google/jedo/IncDep. Since we write the class files to a separate directory, the compiler just sort of fixes the issue with the screwed up source folder.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:48:39 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.