Benjamin,

I suppose the result makes sense. In essence, Maven is becoming
multi-threaded. What about wrapping the LinkedHashMap instances with
Collections.synchronizedList()? Perhaps it is a natural progression of
Maven's stability: 2.0.9 introduced one LinkedHashMap, 2.0.10
converted them all, and now 2.1 should probably synchronize on them.

Paul

On Sat, Feb 21, 2009 at 8:06 AM, Benjamin Bentmann
<benjamin.bentm...@udo.edu> wrote:
> Hi,
>
> seems like our fears have come true, Hudson just spit out the first issue
> that seems to be caused by the introduction of the parallel artifact
> resolution:
>
>> [java] java.util.ConcurrentModificationException
>> [java]  at
>> java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:552)
>> [java]  at java.util.LinkedList$ListItr.next(LinkedList.java:488)
>> [java]  at
>> org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.findConverterForType(DefaultConverterLookup.java:113)
>> [java]  at
>> org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:92)
>> [java]  at
>> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.initSetter(ComponentValueSetter.java:92)
>> [java]  at
>> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.<init>(ComponentValueSetter.java:62)
>> [java]  at
>> org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
>> [java]  at
>> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
>> [java]  at
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:54)
>> [java]  at
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:47)
>> [java]  at
>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(DefaultWagonManager.java:1058)
>> [java]  at
>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(DefaultWagonManager.java:1038)
>> [java]  at
>> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:418)
>> [java]  at
>> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
>> [java]  at
>> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:327)
>> [java]  at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
>> [java]  at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
>> [java]  at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:453)
>> [java]  at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:434)
>> [java]  at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>> [java]  at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>> [java]  at java.lang.Thread.run(Thread.java:534)
>>
>
> The corresponding build [0] appears to be hanging after this error.
>
>
> Benjamin
>
>
> [0]
> https://grid.sonatype.org/ci/job/Maven-2.1.x-bootstrap/jdk=1.4,label=windows/104/console
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to