ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Hachez (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-736) makepom ignores artifact type in ivy.xml and hardcodes 'jar' in the output pom
Date Wed, 10 Feb 2010 23:54:36 GMT

    [ https://issues.apache.org/jira/browse/IVY-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832306#action_12832306
] 

Aaron Hachez commented on IVY-736:
----------------------------------

This issue is also in 2.1.0 release.

This particularly becomes irritating when using Flex + Ant + Ivy

> 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
>            Priority: Minor
>         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.


Mime
View raw message