[ 
https://issues.apache.org/jira/browse/IVYDE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Lalevée resolved IVYDE-293.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalevée

I have found the underlying issue. If there are several resolves happening, and 
some of them are sharing the same ivy.xml, and the workspace resolver is 
enabled, then only one is actually done.
I fixed that.
                
> The 'Resolve all' button in the tool bar does not resolve all Ivyde 
> containers in all projects, just the first Ivyde container in each project
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-293
>                 URL: https://issues.apache.org/jira/browse/IVYDE-293
>             Project: IvyDE
>          Issue Type: Bug
>         Environment: bq.
> Apache Ivy    2.2.1.alpha_20120102010511      
> org.apache.ivy.feature.feature.group    Apache Software Foundation
> Apache Ivy Ant Tasks  2.2.1.alpha_20120102010511      
> org.apache.ivy.eclipse.ant.feature.feature.group        Apache Software 
> Foundation
> Apache IvyDE  2.2.0.201111080039-hudson-200   
> org.apache.ivyde.feature.feature.group  Apache Software Foundation
> Apache IvyDE Resolve Visualizer       2.2.0.201111080039-hudson-200   
> org.apache.ivyde.eclipse.resolvevisualizer.feature.feature.group        
> Apache Software Foundation
> Eclipse 3.7
>            Reporter: GK Ephorus
>            Assignee: Nicolas Lalevée
>              Labels: containers, ivyde, multiple, resolve
>             Fix For: trunk
>
>
> I use multiple Ivyde containers in my Tomcat projects in Eclipse to 
> distinguish between compile-time (e.g. servlet-api + jsp-api) and runtime 
> (e.g. mysql) jars. But only one of the Ivyde containers gets resolved when I 
> hit the 'Resolve all' button.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to