[
http://jira.codehaus.org/browse/MECLIPSE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155730#action_155730
]
Julien Renaut commented on MECLIPSE-377:
----------------------------------------
I think both ways have their benefits.
Common users probably don't want to know about the location of the cache, they
just want it to work and eventually resetting it using the new mojo you're
proposing in MECLIPSE-504.
Still, i've often edited the cache myself to fix wrong entries due to
incorrectly generated artifacts (without sources when they were supposed to
have sources). Having it's location optionally configurable is just for ease of
use.
However, I agree it will work just the same way if you force it to be at the
root of local repo.
Having ACID properties on the file and configurable location would allow the
cache to be stored on a network location. For large teams this could be helpful
but probably not enough to justify the effort.
> 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
