[GRADLE-2177] When a subproject classesDir have been altered, if the subproject is used as a dependency the new output location is not used in the compile classpath Created: 15/Mar/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
Specifying a different project output folder than the default for a source set, such as in the following:
will result in the project being unusable as a dependency. This is currently being used to create an exploded jar in a library directory which we use to share among deployments in JBoss. We specify the dependency as the following:
Our current workaround is to put the output directory into a variable and specify the directory as the following:
Attached is a sample project which displays the issue.
|Comment by Jonathan Imperial [ 17/Apr/12 ]|
Upon further investigating the issue, it appears that the test creates a jar with duplicate files in it. The java compiler doesn't appear to be recognizing this artifact and thus the second subproject doesn't build properly. This seems to be a result of
|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.