[
https://issues.apache.org/jira/browse/IVY-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene resolved IVY-736.
-------------------------------
Assignee: Maarten Coene
Fix Version/s: 2.2.0-RC1
Resolution: Fixed
Fixed in trunk and it will be included in the upcoming 2.2.0-RC1 release.
If possible, please give it a try.
thanks!
Maarten
> makepom ignores artifact type in ivy.xml and hardcodes 'jar' in the output pom
> ------------------------------------------------------------------------------
>
> Key: IVY-736
> URL: https://issues.apache.org/jira/browse/IVY-736
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0.0-beta-1
> Environment: Windows XP, Java 5
> Reporter: Carlton Brown
> Assignee: Maarten Coene
> Priority: Minor
> Fix For: 2.2.0-RC1
>
> Attachments:
> apache-ivy-2.1.0.src.java.org.apache.ivy.plugins.parser.m2.PomModuleDescriptorWriter.java.patch
>
>
> I'm using <ivy:makepom> to generate pom files for a tarfile. Even though
> ivy.xml declares the package type as 'tar', the makepom task sets the
> packaging type to 'jar':
> Input ivy.xml file fragment:
> <info organisation="myorg" module="hello-package" revision="1.0"/>
> <publications>
> <artifact name="hello-package" type="tar" ext="tar"/>
> <artifact name="hello-package" type="pom" ext="pom"/>
> </publications>
> Output pom file fragment:
> <groupId>myorg</groupId>
> <artifactId>hello-package</artifactId>
> <packaging>jar</packaging>
> <version>1.0</version>
> Upon looking in the Ivy source, I found that the value is hardcoded in the
> method printModuleId in
> org.apache.ivy.plugins.parser.m2.PomModuleDescriptorWriter class:
> out.println(" <packaging>jar</packaging>");
> I did not see any easy way to fix this because it does not look like the type
> attribute is part of the module framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
