ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Commented: (IVY-633) Packaging Data Parsed Incorrectly in Maven 2 POM
Date Sun, 18 May 2008 22:27:55 GMT


Maarten Coene commented on IVY-633:

I've added support for the bundle packaging in Ivy SVN. Could you give it a try?
I'm leaving this issue open because we need a more generic solution for this kind of problem.

> Packaging Data Parsed Incorrectly in Maven 2 POM
> ------------------------------------------------
>                 Key: IVY-633
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Maven Compatibility
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: Luke Majewski
>             Fix For: 2.0
> There is still an issue with some dependencies whose extension is not specified in the
default manner.  The example case is when trying to fetch some camel JARs.
> When trying to get the camel-script-1.2.0 JAR, you see:
> [ivy:retrieve]  ==== public: tried
> [ivy:retrieve]
> Ivy is trying to use the extension "bundle" and not JAR.  This is due to the code fetching
the extension from the <packaging> element of the POM.  The relevant portion of the
POM is here:
> <parent>
>     <groupId>org.apache.camel</groupId>
>     <artifactId>camel-parent</artifactId>
>      <version>1.2.0</version>
> </parent>
> <artifactId>camel-script</artifactId>
> <packaging>bundle</packaging>
> <name>Camel :: Script</name>
> <description>Camel Script support</description>
> Notice the <packaging>bundle</packaging>.  Looking at the POM XSD it seems
like this is a valid POM.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message