If I get time I can try to debug it this weekend - looking at the line numbers in the stack trace, the hang is happening inside the old container:
at org.codehaus.plexus.component.discovery.AbstractComponentDiscoverer.findComponents(AbstractComponentDiscoverer.java:78) https://github.com/sonatype/plexus-containers/blob/plexus-container-default-1.0-alpha-9-stable-1/src/main/java/org/codehaus/plexus/component/discovery/AbstractComponentDiscoverer.java#L78 at org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:717) https://github.com/sonatype/plexus-containers/blob/plexus-container-default-1.0-alpha-9-stable-1/src/main/java/org/codehaus/plexus/DefaultPlexusContainer.java#L717 at org.codehaus.plexus.DefaultPlexusContainer.start(DefaultPlexusContainer.java:779) https://github.com/sonatype/plexus-containers/blob/plexus-container-default-1.0-alpha-9-stable-1/src/main/java/org/codehaus/plexus/DefaultPlexusContainer.java#L779 at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:121) https://github.com/sonatype/plexus-containers/blob/plexus-container-default-1.0-alpha-9-stable-1/src/main/java/org/codehaus/plexus/PlexusTestCase.java#L121 at org.apache.maven.archetype.ui.generation.DefaultArchetypeSelectionQueryerTest.setUp(DefaultArchetypeSelectionQueryerTest.java:44) Not sure why the old container gets into this state, maybe it’s the newer version of classworlds? Or maybe the test classpath needs some additional isolation/tweaking? Also note that if I run the test on its own (-Dtest=DefaultArchetypeSelectionQueryerTest) then it only takes a second or so with 3.2.5. -- Cheers, Stuart On Friday, 20 February 2015 at 12:22, Benson Margulies wrote: > org.codehaus.plexus.component.discovery.PlexusXmlComponentDiscoverer#discoverConfiguration > > Is 'discovering' 57 copies of > jar:file:/Users/benson/.m2/repository/org/apache/maven/maven-core/2.2.1/maven-core-2.2.1.jar!/META-INF/plexus/plexus.xml. > > Reading it over and over is taking a long time. As previously > documented, using a newer copy of plexus leads to problems. > > > > On Fri, Feb 20, 2015 at 6:51 AM, Benson Margulies <[email protected] > (mailto:[email protected])> wrote: > > What I see is: > > > > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.071 > > sec - in > > org.apache.maven.archetype.ui.generation.DefaultArchetypeGenerationConfiguratorTest > > Running > > org.apache.maven.archetype.ui.generation.DefaultArchetypeSelectionQueryerTest > > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 55.357 > > sec - in > > org.apache.maven.archetype.ui.generation.DefaultArchetypeSelectionQueryerTest > > Running > > org.apache.maven.archetype.ui.generation.DefaultArchetypeSelectorTest > > ... > > > > So it appears that DefaultArchetypeSelectorTest gets lost in a loop. > > Hervé, have you poked further? > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > (mailto:[email protected]) > For additional commands, e-mail: [email protected] > (mailto:[email protected]) > >
