I think I have a clue on this issue... Although I did not have so much tpme to dig it in, if m2eclipse and subversion is used together in the same work space then startup initialization ends up with deadlocks, both trying to acquire semaphores.
I have a workspace with three level depth, projects are *not* flat top project has the team nature projects are imported using import maven projects... Regards, Hasan Ceylan Dan Diephouse-2 wrote: > > Not yet unfortunately. I'll let you know if I find anything. > > On Wed, May 14, 2008 at 4:35 PM, Igor Fedorenko <[EMAIL PROTECTED]> > wrote: > >> Dan Diephouse wrote: >> >> >>> On a related note, I'm often getting stuck in an endless "building >>> workspace" step now which seems to be related to the maven plugin. I'm >>> wondering if it might have to do with me switching my project to use >>> target/ >>> instead of target-eclipse/. My hunch is that this is somehow related to >>> me >>> running maven on the command line as well. Thoughts? >>> >>> >> Do you have repeatable way to reproduce endless build? I think I saw this >> problem couple of weeks ago but it went away after I ran "mvn clean >> package" >> from command line and refreshed from eclipse. >> >> -- >> Regards, >> Igor >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > -- > Dan Diephouse > http://mulesource.com | http://netzooid.com/blog > > -- View this message in context: http://www.nabble.com/%22Updating-Maven-Dependencies%22-tp17241582p18197382.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
