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-345) IvyDE 2.2.0.beta1 with Ivy 2.3.0 fails to load multiple Ivy classpath containers in Eclipse
Date Sun, 03 Nov 2013 11:30:17 GMT

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

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

Could you share your .classpath so I can reproduce the error ?

> IvyDE 2.2.0.beta1 with Ivy 2.3.0 fails to load multiple Ivy classpath containers in Eclipse
> -------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-345
>                 URL: https://issues.apache.org/jira/browse/IVYDE-345
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 2.2.0.beta1
>         Environment: Eclipse Platform 3.8.1
>            Reporter: Eric Milles
>
> After updating Ivy to 2.3.0 in Eclipse (IvyDE remains at 2.2.0.beta1), and project with
multiple IvyDE classpath containers defined in the .classpath file will only load the last
one.  For example, I have a project set to load conf 'local' for the test libraries as one
classpath container and conf 'master' for the main application dependencies as another classpath
container (only this container is deployed by WTP).
> Only the 'master' container is showing up now.  If I comment out the 'master' container
in .classpath and Resolve, the 'local' container shows up.  So it is not the .classpath XML
that has a problem.  IvyDE is dropping all but the last container.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message