[GRADLE-2213] Standard jar task generates a jar with duplicate entries if we change the resource output folder. Created: 04/Apr/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 8


 Description   

Hi,

we change the default resource output folder with:

sourceSets.main.output.resourcesDir = sourceSets.main.output.classesDir

and we have the problem, that the generated jar file has everything dupicated. Class files and resources. And I saw that we can't change the source property of the jar task because it's read only. How can we achieve that the standard jar task of the java plugin creates a correct jar file?

Thanks in advance.

Guy

 Comments   
Comment by Tinkerer [ 27/Jun/12 ]

I have the same issue with my jar artifacts produced by my multi-project Gradle (M6) build -

sourceSets {
..
main

{ .. output.classesDir = file("$buildDir/classes") output.resourcesDir = file("$buildDir/classes") }

}

commenting out the output.resourcesDir line produces the desired (jar) artifact. Do classesDir & resourcesDir need to point to different output paths?

Comment by Paul Grove [ 30/Oct/13 ]

This also occurs if the below is in your build file

sourceSets {
        main{   output.resourcesDir = "build/classes/main" }
        test{   output.resourcesDir = "build/classes/test"}
}
Comment by Gui Forget [ 25/Oct/14 ]

Issue #GRADLE-2171 provided a workaround if not a fix for this. I customized my jar task as follows and the duplicate entries were gone:

jar {
    duplicatesStrategy= DuplicatesStrategy.EXCLUDE
}
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:15:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.