[
https://issues.apache.org/jira/browse/IVYDE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543841
]
Xavier Hanin commented on IVYDE-64:
-----------------------------------
For the second point, you're right, there is no need to parse the report when
actually doing a resolve. But the performance overhead isn't very high, so if
it makes the method simpler (always use report parsing), I see no point at
changing this. But if you still see something simpler, go ahead, I'll be glad
to apply the patch :-)
> 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
> Attachments: IVYDE-64-r595956.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.
