[
https://issues.apache.org/jira/browse/IVY-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595317#action_12595317
]
Nicolas Lalevée commented on IVY-633:
-------------------------------------
Jose Noheda found a workaround
(http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/[EMAIL
PROTECTED]).
The dependency that has a "bundle" packaging, make a direct dependency to it in
your module. And add an "artifact" tag specifying you want the type "jar". And
do exclude it in any other dependancy that transitively depends on it.
For instance, this does work:
{code:xml}
<ivy-module version="1.3">
<info organisation="myorg" module="mymodule" />
<dependencies>
<dependency org="org.springframework.security"
name="spring-security-acl" rev="2.0.1">
<artifact name="spring-security-acl" type="jar" />
<exclude module="spring-security-core" />
</dependency>
<dependency org="org.springframework.security"
name="spring-security-taglibs" rev="2.0.1">
<artifact name="spring-security-taglibs" type="jar" />
<exclude module="spring-security-acl" />
<exclude module="spring-security-core" />
</dependency>
<dependency org="org.springframework.security"
name="spring-security-core" rev="2.0.1">
<artifact name="spring-security-core" type="jar" />
</dependency>
</dependencies>
</ivy-module>
{code}
> 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.
