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/
Jan Schoppenhorst wrote:
My version of m2eclipse is 0.9.5.20080717-1821. "Unfortunately" all
external repos work fine at the moment, so I cannot provide a thread
dump right now. When it happens again I will certainly post one. One
thing that might be helpful is that external artifacts which have been
put in our repo by ourself did not had an associated pom.xml, which I
have read in another thread causes a lookup in the other repos. I
remedied that and it seems that that stops most of the annoying
requests. If I get this kind of problem again I might give nexus a try.
What was your reason for switching?
Igor Fedorenko schrieb:
Jan,
Can you please provide some thread dumps when m2e gets into such
"locked" state (see [1]) and exact version of m2e you're using?
Also, you may want to try nexus [2]. I don't think I had a single
build hang since I switched my local dev machine to nexus few months ago.
[1]
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-Howtogenerateathreaddump
[2] http://nexus.sonatype.org/
Jan Schoppenhorst wrote:
Hi,
I have the following problem: I use Archiva 1.0, Maven 2.0.8 and the
m2eclipse plugin. All external repos are mirrored by our Archiva
repo. If one of the external repos is really slow, eclipse hangs
while building the workspace. The reason for the external repo being
slow might be that archiva is requesting one of our locally installed
artifacts from an external repo or just because the external server
is simply busy. Even if i turn our Archiva server off the plugin or
Maven still tries to get each artifact and hangs. This makes it
impossible to continue working (or at least I have to wait a very
very long time). I would like to introduce maven in my company but
this behavior would definitly cause an outcry. I have read that
Archiva 1.1.1 allows to set a timeout. Would that solve the problem
or is that the wrong track? Am I doing anything wrong (besides
turning our Archiva server off). Any help is very much appreciated.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
