Tim,
This is known issue and we recommend to turn source downloading off
after you do that once. There is JIRA issue to improve source
downloading. See MNGECLIPSE-146.
regards,
Eugene
Tim Downey wrote:
Hi,
Rebuild speed in 0.11 of a large multi-module project is quite slow,
perhaps due to trying to download source artifacts. This is
particularly noticeable after forcing a refresh in Eclipse of the
projects. Typically, after synchronizing my Eclipse workspace with
the version control system, it is necessary to Refresh the projects in
Eclipse.
This tends to send the Maven plugin sideways for quite a while
(sometimes over 20 minutes) in what seems like frequent and repeated
attempts to download the java-source artifacts. It is very useful to
have the java source artifacts available, but for many open source
dependencies, the source is not available. In such situations, it
seems like m2Eclipse will repeatedly attempt to contact the repository
to download the artifacts.
Is there anything that can be done to remember artifacts that are
unavailable? It would seem that this could be done in memory so that
restarting Eclipse would have the benefit of looking again in case
artifacts become available.
Regards,
Tim
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
