[GRADLE-1559] buildSrc double compilation Created: 17/May/11 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-3 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Greg Gigon | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Attachments: | project-structure.jpg |
Description |
I have a buildSrc folder in my top leve multi-project build. The thing I noticed is that if I specify a different build file, non standart build.gradle in the same top level folder (gradle -b other.gradle), the buildSrc compiles twice. |
Comments |
Comment by Kirk Stork [ 17/Jun/13 ] |
This is still happening in 1.6. with consequences. Effectively, it makes it impossible to have several different builds in the same project root. Say you have someProject
And you execute gradle -bmyBuild.gradle --settings-file mySettings.gradle foo You go once through :buildSrc with your custom settings, then again through :buildSrc with standard settings, then the build moves on to task foo from myBuild.gradle, but the custom settings where whacked by that second trip through :buildSrc Try it with a mySettings.gradle that has something like this in it: rootProject.setName('CustomRootProject') Then put task foo { println "----------------" println rootProject.name println "I am foo" println "----------------" }as the only task in myBuild.gradle Result: :buildSrc:compileJava UP-TO-DATE BUILD SUCCESSFUL |
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:
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. |