[GRADLE-963] version number not in default jar artifact Created: 08/Jun/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

The user guide says:

15.8.1. Archive naming
The default name for a generated archive is projectName-version.type For example:

However, with the java plugin, the default output of gradle jar in build/libs is
myProj.jar.

Personally, I think it is important that the version number be in the filename. Otherwise it is very easy to accidentally use an older, incompatible version and much harder to keep track of what version is being used by outsiders.

 Comments   
Comment by Philip Crotwell [ 24/Jun/10 ]

Possible that this could be resolved, it was caused by this task:

task newcopyToLib(dependsOn: configurations.default.buildArtifacts,
type: Copy) {
into "$buildDir/output/lib"
from configurations.default
from configurations.default.allArtifacts*.file
}

Adam Murdoch said a better task def that would not cause this would be:

In the above, configurations.default.allArtifacts*.file is being evaluated before the version is set in the subproject. You can fix this using something like:

task newcopyToLib(type: Copy)

{ into "$buildDir/output/lib" from configurations.default from configurations.default.allArtifactFiles }
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:43:23 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.