[ https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360529#comment-360529 ]
Tibor Digana edited comment on SUREFIRE-1132 at 1/2/15 5:33 AM: ---------------------------------------------------------------- {code}package ... does not exist{code} appears in the ordinal build as well: without -T... ? Do you trigger the build with --fail-never or -fn ? I have been looking for issues of maven-compiler-plugin, but every link refered to the same answer: missing dependency which has ... package. You should check if the dependency exists on your Nexus repo and check the dependency exists in the POM which has the compiling problems (don't mean dependencyManagenet, see dependencies section). was (Author: tibor17): {code}package ... does not exist{code} appears in the ordinal build as well: without -T... ? Do you trigger the build with --fail-never or -fn ? I have been looking for issues of maven-compiler-plugin, but every link refered to the same answer: missing dependency which has ... package. You should check if the dependency exists on your Nexus repo and check the dependency exists in the POM which has the compiling problems. > Surefire: regular isolated classloader failures in parallelbuild > ---------------------------------------------------------------- > > Key: SUREFIRE-1132 > URL: https://jira.codehaus.org/browse/SUREFIRE-1132 > Project: Maven Surefire > Issue Type: Bug > Components: classloading > Affects Versions: 2.17 > Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux > windows server 2008 x64 > Maven 3.2.2, 3.2.3, 3.2.5 > Oracle HotSpot JDK 7u25 > Reporter: Alexander Ashitkin > Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt > > > We have a large project of 300+ modules which regularly fails with different > kind of classloading issues in different places in surefire plugin. The issue > is reproduced only with parallel build and is not reproduced in single > threaded. This is a main contributor in build instability for us. All the not > loaded dependnecies are actually present in dependency tree. I attached 3 > different samples of how build fails. > Surefire config: > {code} > <configuration> > <forkCount>0</forkCount> > <!--doesnt work in parrallel build. Causes build > failures with error java.io.IOException: Stream Closed--> > <redirectTestOutputToFile>false</redirectTestOutputToFile> > <useManifestOnlyJar>false</useManifestOnlyJar> > </configuration> > {code} > maven cmd is like install -T 10 > Please advise how to sort this out - ready to run any provided diagnostic > and evaluate any options. > Thanks in advance, Alexander -- This message was sent by Atlassian JIRA (v6.1.6#6162)