[
https://issues.apache.org/jira/browse/IVYDE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703139#action_12703139
]
Nicolas Lalevée commented on IVYDE-164:
---------------------------------------
Here is what I am willing to implement unless there are some objections:
* an IvyDE classpath container will be unique by ivy.xml and conf:
** having ivy.xml[*] configured and trying to add ivy.xml[*] will fail
** having ivy.xml[default] configured and trying to add ivy.xml[test] will be
sucessfull
** having ivy.xml[*] configured and trying to add ivy.xml[test] will fail
* the "add library" action will not just add a container, it will open the
wizard of creation of the container with its fields being already filled. So
instead of one click there will be two, but it is less than the 3+ clicks
needed by the classical "Add library" workflow.
Note: I didn't include the ivysettings and properties in the "uniqueness" check
of the IvyDE classpath container in a project: it seems to me too weird to have
the same ivy.xml and same conf used with just some different settings.
> 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
>
>
> 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.
