[
https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634295#action_12634295
]
Maarten Coene commented on IVYDE-121:
-------------------------------------
It will still be the cause of problems when you have defined additional types
in your own ivy.xml files.
In one of my previous jobs, we had defined some extra types and it was this
setting that caused a lot of problems with the usage of IvyDE, especially when
new types were added.
> IVYDE classpath container should support bundle types by default
> ----------------------------------------------------------------
>
> Key: IVYDE-121
> URL: https://issues.apache.org/jira/browse/IVYDE-121
> Project: IvyDE
> Issue Type: Wish
> Components: classpath container
> Affects Versions: 2.0.0.alpha1
> Reporter: Erik-Berndt Scheper
> Assignee: Nicolas Lalevée
> Fix For: 2.0
>
>
> By default, the ivy classpath container does not support bundle types as jar
> files.
> These are generated automatically by Ivy 2.0 RC1 (and higher) when importing
> maven POMs to an ivy repository.
> Sample based on
> http://repo1.maven.org/maven2/org/springframework/ws/spring-oxm-tiger/1.5.4/spring-oxm-tiger-1.5.4.pom
> {code:xml}
> <publications>
> <artifact name="spring-oxm-tiger" type="bundle" ext="jar" conf="master"/>
> <artifact name="spring-oxm-tiger" type="source" ext="jar" conf="sources"
> m:classifier="sources"/>
> <artifact name="spring-oxm-tiger" type="javadoc" ext="jar" conf="javadoc"
> m:classifier="javadoc"/>
> </publications>
> {code}
> The result is that the jar file is resolved from the ivy file, but not shown
> in the classpath container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
