[GRADLE-732] configurations.archives does not include default jar in java plugin Created: 10/Nov/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Philip Crotwell Assignee: Unassigned
Resolution: Won't Fix Votes: 7


In a java project, configurations.archives does not contain the generated jar for the current project.

The user guide seems to indicate here:
that the "default" configuration will be all runtime dependencies plus
archives. I assumed that this meant that the default java artifact jar
of my project would be part of "default" and so I could do something
like this:

task makeSodSite(dependsOn: jar) << { task ->
myArgs = '--run-once -p sod.prop'

But it doesn't work, with a NoClassDefFoundError. I put in a few
prints, like this:
println configurations.runtime.asPath
println configurations.archives.asPath
println configurations.default.asPath

and found that runtime and default seem to be identical and archives is empty.

Adam Murdoch said...
I think it should always include the jar. Oddly, if you add a project dependency on the default configuration from another project, then it does include the jar, but when you use it from the same project, it does not include the jar.

Comment by Hans Dockter [ 19/Apr/10 ]

This is the ivy way of seeing the world. At the moment we just pass this on as the Gradle behavior. If you are within a module, the published artifacts are not part of the resolve. We don't think this is the way it should be and we will fix it for 1.0.

Comment by Andrew Phillips [ 06/Oct/11 ]

We're using the following (unimaginative ) workaround, and it appears to do the trick:

from configurations.runtime
// include main artifact - see http://issues.gradle.org/browse/GRADLE-732
from "${jar.archivePath}"

I guess in your case you'd be appending "${jar.archivePath}" to whatever classpath you're constructing for the Ant task.

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 11:37:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.