[GRADLE-1200] Generated POM does not contain packaging, organization is simply org.apache.maven.model.Organization.toString() Created: 02/Nov/10 Updated: 26/Jan/17 Resolved: 26/Jan/17
The following pom definition
generates this XML:
The generated XML is missing <packaging>jar</packaging> and the <organization> contains org.apache.maven.model.Organization@371daf60 instead of Joern Huxhorn.
This might be better resembled by two separate issues but it would largely duplicate content so I just submitted a single one for now.
|Comment by René Gröschke (Inactive) [ 09/Jan/11 ]|
FYI: These two problems were discussed at the mailinglist with a workaround I think. have a look at http://email@example.com/msg05368.html. We missed to create this issue here. thanks. René
|Comment by Peter Niederwieser [ 27/Feb/11 ]|
Here is a simple workaround to add a packaging type, tested with 1.0-milestone-1:
For packaging type "jar" this isn't really necessary because "jar" is the default anyway, but for other packaging types (like "pom") it is critical.
|Comment by Peter Niederwieser [ 28/Feb/11 ]|
Here is why packaging = "pom" doesn't work:
1. If project has Java plugin applied, a Jar will be generated (even if the project has no sources), and Gradle will overwrite any packaging type set in the build script with "jar". Apparently Maven doesn't include packaging type "jar" in the generated XML because it is the default.
2. If project has Java plugin not applied, the Maven plugin won't add an install task.
|Comment by Joern Huxhorn [ 01/Mar/11 ]|
Ok, leaving out <packaging>jar</packaging> might be "works as expected"...
Concerning the other issue, the <organization>org.apache.maven.model.Organization@371daf60</organization> thing:
The workaround was to define it like this:
But it's IMHO just that: a workaround for the issue described in this ticket.
|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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Joern Huxhorn [ 18/Nov/16 ]|