[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

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-9
Fix Version/s: None

Type: Bug
Reporter: Jonathan Imperial Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: Zip Archive bugtest.zip    
Issue Links:
Related to GRADLE-1050 Jar task should merge entries, not cr... Resolved


Specifying a different project output folder than the default for a source set, such as in the following:

sourceSets.main {
       output.classesDir=rootProject.deploymentLib + File.separator + archivesBaseName + '.jar'
       output.classesDir=rootProject.deploymentLib + File.separator + archivesBaseName + '.jar'

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:

configure(subprojects.findAll { it.name != 'common-lib'}){
        dependencies {
                compile project(':modules:common-lib')

Our current workaround is to put the output directory into a variable and specify the directory as the following:

configure(subprojects.findAll { it.name != 'common-lib'}){
        dependencies {
                compile files( commonLibJarFolder )

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 GRADLE-1050.

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:14:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.