[
https://issues.apache.org/jira/browse/IVY-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594283#action_12594283
]
Chris Herron commented on IVY-633:
----------------------------------
Would really like to see this resolved. Spring-Security (formerly Acegi) is
using bundle packaging and so is affected by this issue. As you know, Acegi is
a hugely popular framework.
> Packaging Data Parsed Incorrectly in Maven 2 POM
> ------------------------------------------------
>
> Key: IVY-633
> URL: https://issues.apache.org/jira/browse/IVY-633
> 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]
> http://repo1.maven.org/maven2/org/apache/camel/camel-script/1.2.0/camel-script-1.2.0.bundle
> 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.
