[GRADLE-2160] Setting packaging 'bundle' uploadArchives and install rename the artifact to {name}.bundle Created: 08/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Rupert Westenthaler Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Hi

When using gradle to uploadArchives/install artifacts with a POM that uses packaging 'bundle' the JAR artifact gets renamed from "

{name}.jar" to "{name}

.bundle".

Basically I am following the instructions as posted at [1] and "pom.withXml" to ensure that the packaging is set (see also GRADLE-1285)

The build file looks like

apply plugin: 'osgi'
apply plugin: 'maven'
apply plugin: "java"

uploadArchives { //remove test dependencies
repositories['mavenInstaller'].with {
pom.project

{ //pom config similar to [1] //packaging will be ignored anyway }

//ensure 'packaging' tag is set
pom.withXml {
def project = it.asNode()
project.version[0] +

{ // add <packaging> after <version> packaging 'bundle' }

}
//skipped beforeDeployment used for signing
//skipped repository config
}
}

The observed behavior is that during the upload/install (after the beforeDeployment callback) the extension of the jar artifact is changed from .jar to .bundle. sourcecode and javadoc artifacts are not affected

best
Rupert

[1] http://jedicoder.blogspot.com/2011/11/automated-gradle-project-deployment-to.html

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