I now have a "real" windows pc to test that on - so I'll give it a spin
before reverting/fixing.

Kristian


2013/2/12 Benjamin Bentmann <benjamin.bentm...@udo.edu>

> Dennis Lundberg wrote:
>
>  "ExecuteJava" daemon prio=6 tid=0x0000000006a92790 nid=0x1078 waiting on
>> condition [0x000000000a63e000..**0x000000000a63fa10]
>>          at sun.misc.Unsafe.park(Native Method)
>>          at java.util.concurrent.locks.**LockSupport.park(LockSupport.**
>> java:118)
>>          at
>> java.util.concurrent.locks.**AbstractQueuedSynchronizer.**
>> parkAndCheckInterrupt(**AbstractQueuedSynchronizer.**java:716)
>>          at
>> java.util.concurrent.locks.**AbstractQueuedSynchronizer.**
>> doAcquireSharedInterruptibly(**AbstractQueuedSynchronizer.**java:872)
>>          at
>> java.util.concurrent.locks.**AbstractQueuedSynchronizer.**
>> acquireSharedInterruptibly(**AbstractQueuedSynchronizer.**java:1179)
>>          at
>> java.util.concurrent.**CountDownLatch.await(**CountDownLatch.java:199)
>>          at
>> org.apache.maven.artifact.**resolver.**DefaultArtifactResolver.**resolve(
>> **DefaultArtifactResolver.java:**528)
>>
>
> Unless the decision gets made to require Java 1.6 for Maven 3.1+, I
> suggest to revert 1a1fe6d50802713d969ed08d6fa06d**ec53cf90e9, thereby
> allowing the thread pool to actually process its work queue.
>
>
> Benjamin
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org>
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to