[
http://jira.codehaus.org/browse/MECLIPSE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155733#action_155733
]
Julien Renaut commented on MECLIPSE-377:
----------------------------------------
That is probably more interesting than dropping the entire artifact cache but
it looks a bit trickier to implement.
Getting the cache for a given artifact could be retrieved based on the artifact
physical location.
BUT, if that's the kind of information we want to retrieve from our artifacts
(whether there is a source attachment, or a javadoc atachment, or even a custom
attachment) then it's the maven metadata that should indicate the existence of
given attachments. This way, the eclipse plugin would just query the metada
about existing attachments and easily discover if a given source or javadoc can
be retrieved instead of maintening the cache.
> eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than
> once in a multi-project
> ---------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-377
> URL: http://jira.codehaus.org/browse/MECLIPSE-377
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath), Core : Multi-projects
> Affects Versions: 2.4
> Reporter: Steinar Bang
> Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> If you run "mvn eclipse:eclipse -DdownloadSources=true" it attempts to
> download source jars for all projects, even when it has tried (and failed) to
> download the jars in earlier projects. This slows down the goal a lot on
> slow network connections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
