Jan,
I think Igor was just suggesting to install local repository manager
what would proxy all requests to the central repository, so it would be
much faster even when Maven would search external repositories. More
over, if you'll have such proxying repository manager on the localhost
it would eliminate cost of network connection in such cases.
Please also note that this issue is not in m2eclipse, but in Maven
core that m2eclipse is delegating to. We are working together with Maven
core team, but due to some restructuring in the Maven embedder it is
hard to say when it will be fixed.
regards,
Eugene
Jan Schoppenhorst wrote:
Thanks for the answer. The bug[1] seems to have caused the pain.
I do not know what you mean by saying "This behaviour probably
highlights problems in your network infrastructure or instability of
the repository manager." If the pom not being in the repo causes m2e
to search in the external repo why does that highlight a problem in
our network infrastructure? In the mentioned case, the central repo
was slow and querying it because of the missing pom caused the hang.
Igor Fedorenko schrieb:
There is a bug in the version of maven embedder used by m2e, it
always checks missing pom.xml files from all remote repositories
(i.e. multiple times per embedder invocation). This behaviour
probably highlights problems in your network infrastructure or
instability of the repository manager. See [1] for more details.
Originally I switched to nexus because [2] contained all artifacts
that I needed, so I could trim my settings.xml to just two entries
(repository/pluginRepository). Since then I started to use nexus on
my local machine too, mostly to debug deployment scenarios. It barely
use any memory so I just keep it running. (disclaimer, I am
affiliated with Sonatype).
[1] http://jira.codehaus.org/browse/MNGECLIPSE-523
[2] http://repository.sonatype.org/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
