[
https://issues.apache.org/jira/browse/IVYDE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée reopened IVYDE-164:
-----------------------------------
Actually I can still do it.
But then I don't know if it is a bug or a feature, should we allow sevral IvyDE
classpath container in the same project ?
If we allow different container with different resolved configuration, should
we support different container with just a different order of classpath entries
?
> Add Ivy Library command adds classpath container even though it already exists
> ------------------------------------------------------------------------------
>
> Key: IVYDE-164
> URL: https://issues.apache.org/jira/browse/IVYDE-164
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.0.0.beta1
> Reporter: Marko Niemi
> Priority: Minor
> Fix For: 2.0.0.final
>
> Attachments: IvyClasspathUtil.java.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 1. Create ivy.xml file
> 2. Open popup menu with ivy.xml selected
> 3. Select Add Ivy Library
> -> Ivy classpath is added
> 2. Open popup menu with ivy.xml selected
> 3. Select Add Ivy Library
> -> another Ivy classpath is added
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
