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

Xavier Hanin resolved IVYDE-64.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0

> Simplify the resolve process
> ----------------------------
>
>                 Key: IVYDE-64
>                 URL: https://issues.apache.org/jira/browse/IVYDE-64
>             Project: IvyDE
>          Issue Type: Improvement
>          Components: classpath container
>    Affects Versions: 1.3.0
>         Environment: trunk r595956
>            Reporter: Nicolas Lalevée
>             Fix For: 1.3.0
>
>         Attachments: IVYDE-64-r595956.patch, IVYDE-64-r600683.patch
>
>
> The current trunk, the resolve job is first checking manually if the artifact 
> has already been resolved. If not in cache, it let ivy resolve it. And 
> finally it parses the xml reports in the cache.
> So first, as far as I have understood, the manual checking against the cache 
> is not needed, ivy already does it.
> And then ivy produce in Java some resolve report that already contain every 
> needed information, there is no need to parse the reports in cache.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to