You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Michel Nolard (JIRA)" <ji...@apache.org> on 2013/11/26 11:18:46 UTC
[jira] [Updated] (IVYDE-353) IvyDE containers all have the same
name 'Ivy'
[ https://issues.apache.org/jira/browse/IVYDE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michel Nolard updated IVYDE-353:
--------------------------------
Attachment: IvyClasspathContainerImpl.java.diff
Here is a proposed patch which fixes the problem. Many thanks to my colleague which did it very quickly !
> IvyDE containers all have the same name 'Ivy'
> ---------------------------------------------
>
> Key: IVYDE-353
> URL: https://issues.apache.org/jira/browse/IVYDE-353
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.2.0.final
> Environment: Eclipse Indigo
> IvyDE 2.2.0.final
> Ivy 2.3.0.final
> Reporter: Michel Nolard
> Attachments: IvyClasspathContainerImpl.java.diff
>
>
> Since I've updated from IvyDE 2.2.0.beta to 2.2.0.final, when looking in "Project properties>>Build path>>Libraries" and in the tab "Order and Export", all Ivy containers are shown with the same name : "Ivy".
> As we've several Ivy containers per projet (eg. test, build, runtime), this becomes blocking when we need to choose which ones to export or to keep private.
--
This message was sent by Atlassian JIRA
(v6.1#6144)