ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] [Commented] (IVYDE-310) No more "retrieve after resolve"
Date Thu, 28 Jun 2012 09:55:44 GMT


Nicolas Lalevée commented on IVYDE-310:

The feature still exists but under another form. There is now a clear separation between building
a classpath to be used by Eclipse for compile and run, and on the other part retrieving artifacts
in some folder.
Building a classpath, is the feature already well known, not changed much in the UI.
Retrieving files in done in a separate UI, since this feature is applicable to non java project.
See the documentation about its use:

If things worked correctly while upgrading IvyDE, a retrieve setup is configured for your
"runtime" configuration. It is named 'dependencies', and should be available in the context
menu as "Retrieve 'dependencies'".

If there is something lacking, it is the automation of both. There is no one action to do
both. It means that if you change your ivy.xml, you should launch 'Ivy'>'Resolve' and 'Ivy'>'Retrieve
So an action 'resolve and retrieve them all' might be missing, but I would consider an improvement
rather than a bug ;)

> No more "retrieve after resolve"
> --------------------------------
>                 Key: IVYDE-310
>                 URL:
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 2.2.0.beta1
>            Reporter: Cédric Damioli
> I just upgraded IvyDE to 2.2.0beta1 and discovered that the "do retrieve after resolve"
feature has been removed.
> I actually used it a lot to seperate "compile" and "runtime" configuration, with eg.
the servlet.jar in the compile configuration and not in the runtime one.
> This is exactly the issue IVYDE-53 opened by Sébastien a while ago that was resolved
and worked great.
> Would it be possible to bring back this feature ? Or do I have to downgrade to previous
version ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message