ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVYDE-121) IVYDE classpath container should support bundle types by default
Date Wed, 24 Sep 2008 11:54:44 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634114#action_12634114
] 

Nicolas Lalevée commented on IVYDE-121:
---------------------------------------

The current UI allow you to specify as many type as you want, there is no feature missing
here. What you are suggesting is about a use case where there will be so many different kind
of type that have to be included to the classpath that the "accept" logic should be reverse:
we would need an excluding a list more than an accepting a list.
But I don't know such use case. So it seems to me a useless complication of the UI.

> 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.


Mime
View raw message