I see where the problem is... in the method printModuleId in
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorWriter class, the
module type is hardcoded:
out.println(" <packaging>jar</packaging>");
Is anyone aware of an existing jira on this?
-----Original Message-----
From: Brown, Carlton [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 14, 2008 1:55 PM
To: [email protected]
Subject: Is packaging type configurable for makepom?
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>
Is it a bug? Is there anything I can do about it? The docs don't seem
to describe any of the mapping process except for how conf gets mapped
to scope.
Thanks,
Carlton
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
