reading your stack trace.
No that's not part of maven core.
Maven core define a version you can override.
So as Core 2.2.1 is a bit old it comes with old surefire version
Except if you override that in your pom.
On 25 November 2013 16:32, Sergey Bondarenko wrote:
> I use Surefire 2.16, and the
I use Surefire 2.16, and the problem is reproducible with that version. Why
do you think it is Surefire? Isn't that package part of Maven Core?
Thanks,
Sergey
2013/11/24 Olivier Lamy
> sounds more an issue in surefire plugin.
> Try use last version of this plugin. (2.16)
>
>
>
> On 25 November
sounds more an issue in surefire plugin.
Try use last version of this plugin. (2.16)
On 25 November 2013 15:29, Sergey Bondarenko wrote:
> Hi Olivier,
>
> The package is part of apache-maven-2.2.1/lib/maven-2.2.1-uber.jar.
> It looks like it is a part of Maven Core (at least it is a part of sta
Hi Olivier,
The package is part of apache-maven-2.2.1/lib/maven-2.2.1-uber.jar.
It looks like it is a part of Maven Core (at least it is a part of standard
distribution).
I do not know why the attached thread dump did not work for you, so I am
sending it as a pastebin: http://pastebin.com/T1MAkwL
Within Maven core or a plugin? I'm not sure Maven core use that..
BTW Hard to know without any logs and/or stack trace or/and the Maven
version you are using.
On 22 November 2013 06:16, Sergey Bondarenko wrote:
> Good afternoon,
>
> I have caught a deadlock in Maven several times, when it was
Good afternoon,
I have caught a deadlock in Maven several times, when it was executing
TestNG tests (see the thread dump attached).
It was happening in
hidden.edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue.
Do you think it is a defect in this concurrency back-port?
Is there a
