You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2009/02/09 18:34:59 UTC
[jira] Resolved: (IVYDE-161) REGRESSION: Resolving does no longer
respect configurations
[ https://issues.apache.org/jira/browse/IVYDE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-161.
-----------------------------------
Resolution: Fixed
Assignee: Nicolas Lalevée
fixed in trunk, along with some fix about hazardous merging of configuration set.
Could you give a try with the last build ?
> REGRESSION: Resolving does no longer respect configurations
> -----------------------------------------------------------
>
> Key: IVYDE-161
> URL: https://issues.apache.org/jira/browse/IVYDE-161
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.0.0.final
> Reporter: Martin Eigenbrodt
> Assignee: Nicolas Lalevée
> Priority: Blocker
> Fix For: 2.0.0.final
>
>
> This happens in the current trunk. I think the bug was introduced with the fix for IVYDE-140.
> IvyDe now seems to merge the configurations from resolve and "retrieve after resolve" event if "retrieve after resolve" is not enabled.
> I've marked this blocker since a central and once working feature does no longer work.
> *How to Reproduce:*
> Add a IvyDe Classpath Container for an ivy.xml with multiple configurations but set Ivy to Resolve only one of them.
> Leave the "Retrieve after resolve" Option unchecked.
> IvyDe will resolve *all* configurations.
> *Workaround:*
> Activate Retrieve after resolve and enter the correct configuration a second time. You willl endup with resolved artifacst but IvyDe will now only resolve the wanted confiugration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.