[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360860#comment-360860
]
Tibor Digana commented on SUREFIRE-1132:
not necessary to use if ( file.exists() ), because isFile and isDirectory
internally performs exists() and some native calls as well.
So you need only the body of the branch and you may print + e: file.exists().
The IsolatedCL has a method like addUrl(). You may log this for the interest
what's coming inside the ICL.
You may log the boolean parame of IsolatedCL constructor. Then we would have
almost all.
{code}
if ( file.exists() )
{
System.err.println( url + f: + file.isFile()
+ d: + file.isDirectory() + r: +
file.canRead() );
}
{code}
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MPMD-200) Regression: Rule:UnusedPrivateMethod
[ https://jira.codehaus.org/browse/MPMD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360871#comment-360871 ] Michael Osipov commented on MPMD-200: - Can you please retry with the latest trunk? Regression: Rule:UnusedPrivateMethod Key: MPMD-200 URL: https://jira.codehaus.org/browse/MPMD-200 Project: Maven PMD Plugin Issue Type: Bug Components: PMD Affects Versions: 3.3 Reporter: Alexey Markevich Attachments: maven-pmd-unused-private-method.zip After upgrade from 3.1 to 3.3 there is failure detection: [INFO] PMD Failure: test.Test:23 Rule:UnusedPrivateMethod Priority:3 Avoid unused private methods such as 'createException(Exception)'.. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360877#comment-360877
]
Tibor Digana commented on SUREFIRE-1132:
Try to print the class path from manifest like this:
{code}
Manifest manifest = new Manifest( clazz.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
You should have JUnit jar there.
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MSHARED-396) Created manifest contains versions of test scope
[ https://jira.codehaus.org/browse/MSHARED-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360879#comment-360879 ] Ittai Zeidman commented on MSHARED-396: --- Hi, I've actually given it some more thought and I think that my suggestion isn't correct since it can cause fragmentation between test and runtime classpaths. Instead I will open a ticket to maven core to allow custom algorithms for dependency conflict resolution. Created manifest contains versions of test scope Key: MSHARED-396 URL: https://jira.codehaus.org/browse/MSHARED-396 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Ittai Zeidman Attachments: dependency-bug.zip Hi, I'm not 100% sure this issue belongs here and not in maven-project itself but seeing as this is where I'm having the issue I thought I'd start here. When building the classpath for a manifest the chosen version of an artifact is based on all scopes and not only on compile/runtime. This is an issue in the following layout: Main-Artifact test-dependency-which-directly-depends-on-old-javassist (test) javassist: 3.15.0-GA compile-dependency-which-transitively-depends-on-new-javassist (compile) dependency-which-directly-depends-on-new-javassist javassist: 3.16.1-GA I'm getting javassist 3.15.0-GA in my classpath and getting a method not found during runtime when using methods from the newer version. I would expect maven to do the nearest path resolution on the subset of artifacts which actually compete on the same classpath (i.e. runtime). I know that maven-archiver is just using project.getRuntimeClasspathElements which uses project.getArtifacts which returns the old version but I think maven-archiver can decide to use a different resolution mechanism. I say this because we also use the maven-assembly-plugin to copy the dependencies and that does the correct, IMO, resolution. I've attached a multi-module project which demonstrates this. Simply run jar:jar in the main-artifact module and take a look in the manifest file of that jar [I'm using archiver via jar-plugin since that is my use-case]. I'm really willing to try and submit a patch or even just test-cases but I wanted to know what you think of the issue first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360883#comment-360883
]
Alexander Ashitkin commented on SUREFIRE-1132:
--
Ok, after adding some logging it looks like the issues goues to the
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath. In
my case for some reasons generateTestClasspath returned empty classpath. i
suspect the cause is org.apache.maven.project.MavenProject#getArtifacts
implementation issue. Please notice issue which alos shows that getArtifacts
could unxpectedly has null value -MJAR-192.
I have added additionall logging and will continue investigation
thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MNGSITE-219) Broken link to 'Generate PGP' docs
[
https://jira.codehaus.org/browse/MNGSITE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MNGSITE-219:
--
Assignee: Michael Osipov
Broken link to 'Generate PGP' docs
--
Key: MNGSITE-219
URL: https://jira.codehaus.org/browse/MNGSITE-219
Project: Maven Project Web Site
Issue Type: Bug
Environment: all
Reporter: Dan Rollo
Assignee: Michael Osipov
Priority: Minor
See the guide located here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Under the section: 'PGP Signature', there is a broken link to a 'Generate
PGP' how-to: Read How to Generate PGP Signatures with Maven for more
information.
The file:
http://svn.apache.org/repos/asf/maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt
currently contains:
Read
{{{https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven}How
to Generate PGP Signatures with Maven}}
for more information.
but should instead contain:
Read
{{{http://central.sonatype.org/pages/working-with-pgp-signatures.html}Working
with PGP Signatures}}
for more information.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360877#comment-360877
]
Tibor Digana edited comment on SUREFIRE-1132 at 1/7/15 7:26 AM:
Try to print the class path from manifest like this:
{code}
Manifest manifest = new Manifest( ForkedBooter.class.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ) );
{code}
You should have JUnit jar there.
was (Author: tibor17):
Try to print the class path from manifest like this:
{code}
Manifest manifest = new Manifest( ForkedBooter.class.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
You should have JUnit jar there.
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MNGSITE-219) Broken link to 'Generate PGP' docs
[
https://jira.codehaus.org/browse/MNGSITE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNGSITE-219.
--
Resolution: Fixed
Thanks, fixed with http://svn.apache.org/r1650049.
Broken link to 'Generate PGP' docs
--
Key: MNGSITE-219
URL: https://jira.codehaus.org/browse/MNGSITE-219
Project: Maven Project Web Site
Issue Type: Bug
Environment: all
Reporter: Dan Rollo
Assignee: Michael Osipov
Priority: Minor
See the guide located here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Under the section: 'PGP Signature', there is a broken link to a 'Generate
PGP' how-to: Read How to Generate PGP Signatures with Maven for more
information.
The file:
http://svn.apache.org/repos/asf/maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt
currently contains:
Read
{{{https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven}How
to Generate PGP Signatures with Maven}}
for more information.
but should instead contain:
Read
{{{http://central.sonatype.org/pages/working-with-pgp-signatures.html}Working
with PGP Signatures}}
for more information.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360876#comment-360876
]
Tibor Digana commented on SUREFIRE-1132:
I guess it will be JUnit4Provider.
Is not it?
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360877#comment-360877
]
Tibor Digana edited comment on SUREFIRE-1132 at 1/7/15 6:37 AM:
Try to print the class path from manifest like this:
{code}
Manifest manifest = new Manifest( ForkedBooter.class.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
You should have JUnit jar there.
was (Author: tibor17):
Try to print the class path from manifest like this:
{code}
Manifest manifest = new Manifest( clazz.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
You should have JUnit jar there.
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360880#comment-360880
]
Alexander Ashitkin edited comment on SUREFIRE-1132 at 1/7/15 7:43 AM:
--
{quote}
I guess it will be JUnit4Provider.
{quote}
i think so. I didnt log startup configuration but in ProviderConfiguration i
can see property
'providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider':
{code}ProviderConfiguration{dirScannerParams=org.apache.maven.surefire.testset.DirectoryScannerParameters@31befd9f,
reporterConfiguration=org.apache.maven.surefire.report.ReporterConfiguration@1c20c684,
testArtifact=org.apache.maven.surefire.testset.TestArtifactInfo@1fb3ebeb,
testSuiteDefinition=org.apache.maven.surefire.testset.TestRequest@548c4f57,
runOrderParameters=org.apache.maven.surefire.testset.RunOrderParameters@1218025c,
providerProperties={testClassesDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
useManifestOnlyJar=false,
classPathUrl.1=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes,
reportsDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\surefire-reports,
classPathUrl.0=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
rerunFailingTestsCount=0,
providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider,
testSuiteDefinitionTestSourceDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\src\test\java,
surefireClassPathUrl.1=d:\.m2\repository\org\apache\maven\surefire\surefire-api\2.19-SNAPSHOT\surefire-api-2.19-SNAPSHOT.jar,
surefireClassPathUrl.0=d:\.m2\repository\org\apache\maven\surefire\surefire-junit4\2.19-SNAPSHOT\surefire-junit4-2.19-SNAPSHOT.jar,
runOrder=filesystem, tc.12=...Test, tc.11=...Test, useSystemClassLoader=true,
tc.10=...Test, excludes0=**/*ITest.java, tc.9=...Test, tc.8=...Test,
tc.7=...Test, tc.6=...Test, tc.5=...Test, isTrimStackTrace=true, tc.4=...Test,
tc.3=...Test, tc.2=...Test, tc.1=...Test, tc.0=...Test,
includes2=**/*TestCase.java, enableAssertions=true, includes1=**/*Test.java,
failIfNoTests=false,
runStatisticsFile=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\.surefire-4E2BB134B213C67EDAB88B93ED52F132211C1F4A,
includes0=**/Test*.java, preferTestsFromInStream=false,
childDelegation=false}, failIfNoTests=false, forkTestSet=null,
readTestsFromInStream=false{code}
{code}
Manifest manifest = new Manifest( ForkedBooter.class.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
this returns 'CLASS PATH:null'. Actually we use useManifestOnlyJar=false so i
dont expect to see something here (and what about jars ordering?)
Please notice, when i run build sucessfully, is see all jars in the output,
including all dependencies unlike of the reported case. So classloader is set
up incorrectly. Forked booter starts with incomplete classpath and issue comes
to bootstrapping logic - how classpath is created and passed to the fork.
incorrectly shared files or system properties could result in such failures in
parallel env.
thank you
was (Author: alex_ashitkin):
{quote}
I guess it will be JUnit4Provider.
{quote}
i think so. I didnt log startup configuration but in ProviderConfiguration i
can see property
'providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider':
{code}ProviderConfiguration{dirScannerParams=org.apache.maven.surefire.testset.DirectoryScannerParameters@31befd9f,
reporterConfiguration=org.apache.maven.surefire.report.ReporterConfiguration@1c20c684,
testArtifact=org.apache.maven.surefire.testset.TestArtifactInfo@1fb3ebeb,
testSuiteDefinition=org.apache.maven.surefire.testset.TestRequest@548c4f57,
runOrderParameters=org.apache.maven.surefire.testset.RunOrderParameters@1218025c,
providerProperties={testClassesDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
useManifestOnlyJar=false,
classPathUrl.1=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes,
reportsDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\surefire-reports,
classPathUrl.0=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
rerunFailingTestsCount=0,
providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider,
testSuiteDefinitionTestSourceDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\src\test\java,
surefireClassPathUrl.1=d:\.m2\repository\org\apache\maven\surefire\surefire-api\2.19-SNAPSHOT\surefire-api-2.19-SNAPSHOT.jar,
surefireClassPathUrl.0=d:\.m2\repository\org\apache\maven\surefire\surefire-junit4\2.19-SNAPSHOT\surefire-junit4-2.19-SNAPSHOT.jar,
runOrder=filesystem, tc.12=...Test, tc.11=...Test, useSystemClassLoader=true,
tc.10=...Test, excludes0=**/*ITest.java, tc.9=...Test, tc.8=...Test,
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360880#comment-360880
]
Alexander Ashitkin commented on SUREFIRE-1132:
--
{quote}
I guess it will be JUnit4Provider.
{quote}
i think so. I didnt log startup configuration but in ProviderConfiguration i
can see property
'providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider':
{code}ProviderConfiguration{dirScannerParams=org.apache.maven.surefire.testset.DirectoryScannerParameters@31befd9f,
reporterConfiguration=org.apache.maven.surefire.report.ReporterConfiguration@1c20c684,
testArtifact=org.apache.maven.surefire.testset.TestArtifactInfo@1fb3ebeb,
testSuiteDefinition=org.apache.maven.surefire.testset.TestRequest@548c4f57,
runOrderParameters=org.apache.maven.surefire.testset.RunOrderParameters@1218025c,
providerProperties={testClassesDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
useManifestOnlyJar=false,
classPathUrl.1=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes,
reportsDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\surefire-reports,
classPathUrl.0=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
rerunFailingTestsCount=0,
providerConfiguration=org.apache.maven.surefire.junit4.JUnit4Provider,
testSuiteDefinitionTestSourceDirectory=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\src\test\java,
surefireClassPathUrl.1=d:\.m2\repository\org\apache\maven\surefire\surefire-api\2.19-SNAPSHOT\surefire-api-2.19-SNAPSHOT.jar,
surefireClassPathUrl.0=d:\.m2\repository\org\apache\maven\surefire\surefire-junit4\2.19-SNAPSHOT\surefire-junit4-2.19-SNAPSHOT.jar,
runOrder=filesystem, tc.12=...Test, tc.11=...Test, useSystemClassLoader=true,
tc.10=...Test, excludes0=**/*ITest.java, tc.9=...Test, tc.8=...Test,
tc.7=...Test, tc.6=...Test, tc.5=...Test, isTrimStackTrace=true, tc.4=...Test,
tc.3=...Test, tc.2=...Test, tc.1=...Test, tc.0=...Test,
includes2=**/*TestCase.java, enableAssertions=true, includes1=**/*Test.java,
failIfNoTests=false,
runStatisticsFile=D:\jenkins\work\workspace\sf-2.18.1-test\my-server\.surefire-4E2BB134B213C67EDAB88B93ED52F132211C1F4A,
includes0=**/Test*.java, preferTestsFromInStream=false,
childDelegation=false}, failIfNoTests=false, forkTestSet=null,
readTestsFromInStream=false{code}
{code}
Manifest manifest = new Manifest( ForkedBooter.class.getResourceAsStream(
/META-INF/MANIFEST.MF ) );
System.out.println( CLASS PATH: + manifest.getMainAttributes().getValue(
Class-Path ));
{code}
this returns 'CLASS PATH:null'. Actually we use useManifestOnlyJar=false so i
dont expect to see something here (and what about jars ordering?)
Please notice, when i run build sucessfully, is see all jars in the output,
including all dependencies unlike of the reported case. So classloader is set
up incorrectly. Forked booter starts with incomplete classpath and issue comes
to bootstrapping logic - how classpath is created and passed to the fork.
incorrectly shared files or system properties could result in such failures in
parallel env.
thank you
thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MJAR-192) Sporadic NPE in maven-jar-plugin:2.5:jar
[
https://jira.codehaus.org/browse/MJAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360884#comment-360884
]
Alexander Ashitkin commented on MJAR-192:
-
Please notice the issue SUREFIRE-1132 which also traced down to mp cause in
MavenProject#getArtifacts
Sporadic NPE in maven-jar-plugin:2.5:jar
Key: MJAR-192
URL: https://jira.codehaus.org/browse/MJAR-192
Project: Maven JAR Plugin
Issue Type: Bug
Affects Versions: 2.5
Environment: win 2008 server x64 java 8u25 maven 3.2.5
Reporter: Alexander Ashitkin
Strange npe at jar goal:
{code}
16:41:50 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on project
my-model: Error assembling JAR: NullPointerException - [Help 1]
16:41:50 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar)
on project my-model: Error assembling JAR
16:41:50 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
16:41:50 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
16:41:50 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
16:41:50 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
16:41:50 at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
16:41:50 at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
16:41:50 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
16:41:50 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
16:41:50 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
16:41:50 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
16:41:50 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
16:41:50 at java.lang.Thread.run(Thread.java:745)
16:41:50 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
assembling JAR
16:41:50 at
org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233)
16:41:50 at
org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251)
16:41:50 at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
16:41:50 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
16:41:50 ... 11 more
16:41:50 Caused by: java.lang.NullPointerException
16:41:50 at
org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:715)
16:41:50 at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1218)
16:41:50 at
org.apache.maven.project.MavenProject.init(MavenProject.java:197)
16:41:50 at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
16:41:50 at
org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226)
16:41:50 ... 14 more
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360935#comment-360935
]
Alexander Ashitkin edited comment on SUREFIRE-1132 at 1/8/15 1:38 AM:
--
Hi Tibor
with additional logging in
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath i
captured what indeed {code}SetArtifact classpathArtifacts =
getProject().getArtifacts();{code} in a case of failure returns empty set. My
log output is :
{code}
Project artifacts: []
Project classpath:
[D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes]
{code}
The code to capture data, as following:
{code}
Classpath generateTestClasspath()
throws InvalidVersionSpecificationException, MojoFailureException,
ArtifactResolutionException,
ArtifactNotFoundException, MojoExecutionException
{
ListString classpath = new ArrayListString( 2 +
getProject().getArtifacts().size() );
classpath.add( getTestClassesDirectory().getAbsolutePath() );
classpath.add( getClassesDirectory().getAbsolutePath() );
@SuppressWarnings( unchecked ) SetArtifact classpathArtifacts =
getProject().getArtifacts();
System.out.println( Project artifacts: + classpathArtifacts );
if ( getClasspathDependencyScopeExclude() != null
!getClasspathDependencyScopeExclude().equals( ) )
{
ArtifactFilter dependencyFilter = new ScopeArtifactFilter(
getClasspathDependencyScopeExclude() );
classpathArtifacts = this.filterArtifacts( classpathArtifacts,
dependencyFilter );
}
if ( getClasspathDependencyExcludes() != null )
{
ArtifactFilter dependencyFilter =
new PatternIncludesArtifactFilter( Arrays.asList(
getClasspathDependencyExcludes() ) );
classpathArtifacts = this.filterArtifacts( classpathArtifacts,
dependencyFilter );
}
for ( Artifact artifact : classpathArtifacts )
{
if ( artifact.getArtifactHandler().isAddedToClasspath() )
{
File file = artifact.getFile();
if ( file != null )
{
classpath.add( file.getPath() );
}
}
}
// Add additional configured elements to the classpath
if ( getAdditionalClasspathElements() != null )
{
for ( String classpathElement : getAdditionalClasspathElements() )
{
if ( classpathElement != null )
{
classpath.add( classpathElement );
}
}
}
// adding TestNG MethodSelector to the classpath
// Todo: move
if ( getTestNgArtifact() != null )
{
addTestNgUtilsArtifacts( classpath );
}
System.out.println( Project classpath: + classpath );
return new Classpath( classpath );
}
{code}
At this point surefire issue could be closed and i will look forward to raise
it aganist maven core
thank you
was (Author: alex_ashitkin):
Hi Tibor
with additional logging in
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath i
captured what indeed {code}SetArtifact classpathArtifacts =
getProject().getArtifacts();{code} in a case of failure returns nothing. My log
output is :
{code}
Project artifacts: []
Project classpath:
[D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes]
{code}
The code to capture data, as following:
{code}
Classpath generateTestClasspath()
throws InvalidVersionSpecificationException, MojoFailureException,
ArtifactResolutionException,
ArtifactNotFoundException, MojoExecutionException
{
ListString classpath = new ArrayListString( 2 +
getProject().getArtifacts().size() );
classpath.add( getTestClassesDirectory().getAbsolutePath() );
classpath.add( getClassesDirectory().getAbsolutePath() );
@SuppressWarnings( unchecked ) SetArtifact classpathArtifacts =
getProject().getArtifacts();
System.out.println( Project artifacts: + classpathArtifacts );
if ( getClasspathDependencyScopeExclude() != null
!getClasspathDependencyScopeExclude().equals( ) )
{
ArtifactFilter dependencyFilter = new ScopeArtifactFilter(
getClasspathDependencyScopeExclude() );
classpathArtifacts = this.filterArtifacts( classpathArtifacts,
dependencyFilter );
}
if ( getClasspathDependencyExcludes() != null )
{
ArtifactFilter dependencyFilter =
new PatternIncludesArtifactFilter( Arrays.asList(
getClasspathDependencyExcludes() ) );
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MNG-5750:
Description:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
was:
We have a large project of 300+ modules which regularly fails with different
kind of classloading issues in different places. The issue is reliably
reproduced only with parallel build and is not happens in single threaded. The
optimal concurrency level for our project ~10 threads. At this level ~%20 of
builds fail. To workaround the issue we reduced concurrency to 4 in development
builds and reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
Sporadic failures in concurrent build
-
Key: MNG-5750
URL: https://jira.codehaus.org/browse/MNG-5750
Project: Maven
Issue Type: Bug
Components: General
Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
HotSpot JDK 7u25
windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
Reporter: Alexander Ashitkin
Priority: Critical
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20
[jira] (MNG-5750) Sporadic failures in concurrent build
Alexander Ashitkin created MNG-5750:
---
Summary: Sporadic failures in concurrent build
Key: MNG-5750
URL: https://jira.codehaus.org/browse/MNG-5750
Project: Maven
Issue Type: Bug
Components: General
Affects Versions: 3.2.5, 3.2.2, 3.2.1, 3.1.1
Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
HotSpot JDK 7u25
windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
Reporter: Alexander Ashitkin
Priority: Critical
We have a large project of 300+ modules which regularly fails with different
kind of classloading issues in different places. The issue is reliably
reproduced only with parallel build and is not happens in single threaded. The
optimal concurrency level for our project ~10 threads. At this level ~%20 of
builds fail. To workaround the issue we reduced concurrency to 4 in development
builds and reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360935#comment-360935
]
Alexander Ashitkin commented on SUREFIRE-1132:
--
Hi Tibor
with additional logging in
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath i
captured what indeed {code}SetArtifact classpathArtifacts =
getProject().getArtifacts();{code} in a case of failure returns nothing. My log
output is :
{code}
Project artifacts: []
Project classpath:
[D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\test-classes,
D:\jenkins\work\workspace\sf-2.18.1-test\my-server\target\classes]
{code}
The code to capture data, as following:
{code}
Classpath generateTestClasspath()
throws InvalidVersionSpecificationException, MojoFailureException,
ArtifactResolutionException,
ArtifactNotFoundException, MojoExecutionException
{
ListString classpath = new ArrayListString( 2 +
getProject().getArtifacts().size() );
classpath.add( getTestClassesDirectory().getAbsolutePath() );
classpath.add( getClassesDirectory().getAbsolutePath() );
@SuppressWarnings( unchecked ) SetArtifact classpathArtifacts =
getProject().getArtifacts();
System.out.println( Project artifacts: + classpathArtifacts );
if ( getClasspathDependencyScopeExclude() != null
!getClasspathDependencyScopeExclude().equals( ) )
{
ArtifactFilter dependencyFilter = new ScopeArtifactFilter(
getClasspathDependencyScopeExclude() );
classpathArtifacts = this.filterArtifacts( classpathArtifacts,
dependencyFilter );
}
if ( getClasspathDependencyExcludes() != null )
{
ArtifactFilter dependencyFilter =
new PatternIncludesArtifactFilter( Arrays.asList(
getClasspathDependencyExcludes() ) );
classpathArtifacts = this.filterArtifacts( classpathArtifacts,
dependencyFilter );
}
for ( Artifact artifact : classpathArtifacts )
{
if ( artifact.getArtifactHandler().isAddedToClasspath() )
{
File file = artifact.getFile();
if ( file != null )
{
classpath.add( file.getPath() );
}
}
}
// Add additional configured elements to the classpath
if ( getAdditionalClasspathElements() != null )
{
for ( String classpathElement : getAdditionalClasspathElements() )
{
if ( classpathElement != null )
{
classpath.add( classpathElement );
}
}
}
// adding TestNG MethodSelector to the classpath
// Todo: move
if ( getTestNgArtifact() != null )
{
addTestNgUtilsArtifacts( classpath );
}
System.out.println( Project classpath: + classpath );
return new Classpath( classpath );
}
{code}
At this point surefire issue could be closed and i will look forward to raise
it aganist maven core
thank you
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, 2.18.1
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/7u65/8u25
Reporter: Alexander Ashitkin
Assignee: Tibor Digana
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing
[ https://jira.codehaus.org/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360930#comment-360930 ] David Hoffer commented on MEAR-212: --- I was able to track down the change in my project that will cause this. My war has a dependency on the following jar artifact. Since I am making a skinny war in the ear, I have to also add this dependency in the ear. Once I do that it causes the error. So its not possible to make a skinny war with this jar dependency. dependency groupIdorg.apache.rampart/groupId artifactIdrampart-core/artifactId typejar/type /dependency Failed to initialize ear modules: Unknown artifact type[mar] for addressing --- Key: MEAR-212 URL: https://jira.codehaus.org/browse/MEAR-212 Project: Maven Ear Plugin Issue Type: Bug Affects Versions: 2.10 Reporter: David Hoffer I'm trying to generate and ear file but I'm getting the following message: Failed to initialize ear modules: Unknown artifact type[mar] for addressing (full debug stack trace is below) However I don't have any mar artifacts in my dependencies. What I do have is a war that has 4 mar files added as resources and I'm making a ear with the skinny war feature. Why would the ear plugin give this error when it has no nothing to do with the mar resources in the war...or perhaps this error has nothing to do with those resources, not sure. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules: Unknown artifact type[mar] for addressing - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize ear modules at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260) at org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown artifact type[mar] for addressing at org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88) at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250) ... 22 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-85) Add m2e mapping
[
https://jira.codehaus.org/browse/MRRESOURCES-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MRRESOURCES-85:
---
Fix Version/s: (was: 1.6)
more-investigation
Add m2e mapping
---
Key: MRRESOURCES-85
URL: https://jira.codehaus.org/browse/MRRESOURCES-85
Project: Maven Remote Resources Plugin
Issue Type: Improvement
Affects Versions: 1.6
Reporter: Karl-Heinz Marbaise
Priority: Minor
Fix For: more-investigation
Add mapping for m2e for plugin something like this.
{code:xml}
?xml version=1.0 encoding=UTF-8?
lifecycleMappingMetadata
pluginExecutions
pluginExecution
pluginExecutionFilter
goals
goalbundle/goal
goalprocess/goal
/goals
/pluginExecutionFilter
action
execute
runOnIncrementaltrue/runOnIncremental
runOnConfigurationtrue/runOnConfiguration
/execute
/action
/pluginExecution
/pluginExecutions
/lifecycleMappingMetadata
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRRESOURCES-92) Upgrade to Maven 3.0 compatiblity
Karl-Heinz Marbaise created MRRESOURCES-92: -- Summary: Upgrade to Maven 3.0 compatiblity Key: MRRESOURCES-92 URL: https://jira.codehaus.org/browse/MRRESOURCES-92 Project: Maven Remote Resources Plugin Issue Type: Improvement Affects Versions: 3.0 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-396) Created manifest contains versions of test scope
[ https://jira.codehaus.org/browse/MSHARED-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ittai Zeidman closed MSHARED-396. - Resolution: Not A Bug I think it's not a bug in maven-archiver but in maven core. see my comment for more details Created manifest contains versions of test scope Key: MSHARED-396 URL: https://jira.codehaus.org/browse/MSHARED-396 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Ittai Zeidman Attachments: dependency-bug.zip Hi, I'm not 100% sure this issue belongs here and not in maven-project itself but seeing as this is where I'm having the issue I thought I'd start here. When building the classpath for a manifest the chosen version of an artifact is based on all scopes and not only on compile/runtime. This is an issue in the following layout: Main-Artifact test-dependency-which-directly-depends-on-old-javassist (test) javassist: 3.15.0-GA compile-dependency-which-transitively-depends-on-new-javassist (compile) dependency-which-directly-depends-on-new-javassist javassist: 3.16.1-GA I'm getting javassist 3.15.0-GA in my classpath and getting a method not found during runtime when using methods from the newer version. I would expect maven to do the nearest path resolution on the subset of artifacts which actually compete on the same classpath (i.e. runtime). I know that maven-archiver is just using project.getRuntimeClasspathElements which uses project.getArtifacts which returns the old version but I think maven-archiver can decide to use a different resolution mechanism. I say this because we also use the maven-assembly-plugin to copy the dependencies and that does the correct, IMO, resolution. I've attached a multi-module project which demonstrates this. Simply run jar:jar in the main-artifact module and take a look in the manifest file of that jar [I'm using archiver via jar-plugin since that is my use-case]. I'm really willing to try and submit a patch or even just test-cases but I wanted to know what you think of the issue first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360886#comment-360886
]
Tibor Digana commented on SUREFIRE-1132:
Exactly, I was about to post the same method #generateTestClasspath() :)
Alexander was faster :)
AbstractSurefireMojo#createStartupConfiguration() creates the configuration
upon artifacts which goes to the ForkStarter.
As we talked with Jason and Kristian about concurrency issue in maven-core few
days ago, I guess you found some concurrency issue.
Jason van Zyl told me that no new concurrency issues present at the moment, but
that was maybe too positive statement...
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MNG-5102) Mixin POM fragments
[ https://jira.codehaus.org/browse/MNG-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360887#comment-360887 ] Christoph Henrici commented on MNG-5102: Unfortunately does e2Eclipse not work with https://github.com/repaint-io/maven-tiles. It simply ignores it. Exactly http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html is simply not enough. Dependency Management is almost more urgent. Mixin POM fragments --- Key: MNG-5102 URL: https://jira.codehaus.org/browse/MNG-5102 Project: Maven Issue Type: Wish Components: FDPFC, POM Affects Versions: 2.2.1 Reporter: Anthony Whitford Fix For: Issues to be reviewed for 4.x Attachments: daddy3.zip, maven-tiles.zip I am looking for a way to _mixin_ POM fragments into POMs. Note that this idea is beyond parent pom inheritance because all projects inherit from a corporate parent pom. The problem that I am running into is that the corporate parent pom is turning into an _everything but the kitchen sink_ POM and I'd like to dissect it into POM fragments relevant for individual modules. For example, I would like to have mixins for: * Java projects (that include static code analysis plugins, javadoc, etc.) * JPA projects (that include DDL generation) * Flex projects (that include flexmojos, asdoc, etc.) * Scala projects (that include the maven-scala-compiler plugin, scaladoc, etc.) * JavaScript projects (that include build plugins like maven-yuicompressor-plugin with jslint and compress goals) Hopefully, you get the idea. Without the ability to factor pom logic, we are left with two symptoms: # copy/paste duplication # complex _it does it all_ parent poms (which slow down builds because more plugins are loaded even though they might not do anything material) Note that a project may include multiple mixins as I could have a project that contains Java code, Scala code, and JavaScript. Another idea is that the mixins could be parameterized, so that the ultimate pom can be customized based on the parameters (like tokens). I recall reading about Mixins coming in Maven 3.1, but could not find any such issue to watch, so am creating one. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360873#comment-360873
]
Alexander Ashitkin commented on SUREFIRE-1132:
--
Hi Tibor.
Please notice i run build with ForkedBooter currently (forkCount=1). Do you
propose to switch on icl and try to reproduce the same?
{quote}
Then we would have almost all.
{quote}
does it mean you have enough info to identify the root cause?
thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MNGSITE-219) Broken link to 'Generate PGP' docs
[
https://jira.codehaus.org/browse/MNGSITE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNGSITE-219:
---
Summary: Broken link to 'Generate PGP' docs (was: DOCO: Broken link to
'Generate PGP' docs)
Broken link to 'Generate PGP' docs
--
Key: MNGSITE-219
URL: https://jira.codehaus.org/browse/MNGSITE-219
Project: Maven Project Web Site
Issue Type: Bug
Environment: all
Reporter: Dan Rollo
Priority: Minor
See the guide located here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Under the section: 'PGP Signature', there is a broken link to a 'Generate
PGP' how-to: Read How to Generate PGP Signatures with Maven for more
information.
The file:
http://svn.apache.org/repos/asf/maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt
currently contains:
Read
{{{https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven}How
to Generate PGP Signatures with Maven}}
for more information.
but should instead contain:
Read
{{{http://central.sonatype.org/pages/working-with-pgp-signatures.html}Working
with PGP Signatures}}
for more information.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1132:
--
Assignee: Tibor Digana
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, 2.18.1
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/7u65/8u25
Reporter: Alexander Ashitkin
Assignee: Tibor Digana
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360889#comment-360889
]
Alexander Ashitkin edited comment on SUREFIRE-1132 at 1/7/15 9:23 AM:
--
Tibor, generally i have no objections, but i would like to wait for reproducing
case. if i will capture unxepected result in generateTestClasspath then this
one could be closed safely. I expect to come back no later than Monday
Also, in such case i would need to raise an issue to fix
MavenProject#getArtifacts - please advise how to do it properly.
Thank you
was (Author: alex_ashitkin):
Tibor, generally i have no objections, but i would like to wait for reproducing
case. if i will capture unxepected result in generateTestClasspath then this
one could be closed safely.
Also, in such case i would need to raise an issue to fix
MavenProject#getArtifacts - please advise how to do it properly.
Thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360890#comment-360890
]
Tibor Digana commented on SUREFIRE-1132:
Ok Alexander, I have already assigned this issue to me to keep my eyes on it.
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, 2.18.1
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/7u65/8u25
Reporter: Alexander Ashitkin
Assignee: Tibor Digana
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing
[ https://jira.codehaus.org/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Hoffer updated MEAR-212: -- Issue Type: Bug (was: New Feature) Failed to initialize ear modules: Unknown artifact type[mar] for addressing --- Key: MEAR-212 URL: https://jira.codehaus.org/browse/MEAR-212 Project: Maven Ear Plugin Issue Type: Bug Affects Versions: 2.10 Reporter: David Hoffer I'm trying to generate and ear file but I'm getting the following message: Failed to initialize ear modules: Unknown artifact type[mar] for addressing (full debug stack trace is below) However I don't have any mar artifacts in my dependencies. What I do have is a war that has 4 mar files added as resources and I'm making a ear with the skinny war feature. Why would the ear plugin give this error when it has no nothing to do with the mar resources in the war...or perhaps this error has nothing to do with those resources, not sure. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules: Unknown artifact type[mar] for addressing - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize ear modules at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260) at org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown artifact type[mar] for addressing at org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88) at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250) ... 22 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing
David Hoffer created MEAR-212: - Summary: Failed to initialize ear modules: Unknown artifact type[mar] for addressing Key: MEAR-212 URL: https://jira.codehaus.org/browse/MEAR-212 Project: Maven Ear Plugin Issue Type: New Feature Reporter: David Hoffer I'm trying to generate and ear file but I'm getting the following message: Failed to initialize ear modules: Unknown artifact type[mar] for addressing (full debug stack trace is below) However I don't have any mar artifacts in my dependencies. What I do have is a war that has 4 mar files added as resources and I'm making a ear with the skinny war feature. Why would the ear plugin give this error when it has no nothing to do with the mar resources in the war...or perhaps this error has nothing to do with those resources, not sure. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules: Unknown artifact type[mar] for addressing - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize ear modules at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260) at org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown artifact type[mar] for addressing at org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88) at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250) ... 22 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing
[ https://jira.codehaus.org/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Hoffer updated MEAR-212: -- Affects Version/s: 2.10 Failed to initialize ear modules: Unknown artifact type[mar] for addressing --- Key: MEAR-212 URL: https://jira.codehaus.org/browse/MEAR-212 Project: Maven Ear Plugin Issue Type: New Feature Affects Versions: 2.10 Reporter: David Hoffer I'm trying to generate and ear file but I'm getting the following message: Failed to initialize ear modules: Unknown artifact type[mar] for addressing (full debug stack trace is below) However I don't have any mar artifacts in my dependencies. What I do have is a war that has 4 mar files added as resources and I'm making a ear with the skinny war feature. Why would the ear plugin give this error when it has no nothing to do with the mar resources in the war...or perhaps this error has nothing to do with those resources, not sure. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules: Unknown artifact type[mar] for addressing - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml (default-generate-application-xml) on project coreservices-ear: Failed to initialize ear modules at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize ear modules at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260) at org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown artifact type[mar] for addressing at org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88) at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250) ... 22 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360888#comment-360888
]
Tibor Digana commented on SUREFIRE-1132:
Any objections to close this issue?
Pls keep track with https://jira.codehaus.org/browse/MJAR-192.
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MEAR-211) Support flexible ways of adding arbitrary content to ear
David Hoffer created MEAR-211: - Summary: Support flexible ways of adding arbitrary content to ear Key: MEAR-211 URL: https://jira.codehaus.org/browse/MEAR-211 Project: Maven Ear Plugin Issue Type: New Feature Reporter: David Hoffer I'm finding it really difficult to add a few files to the APP-INF folder in an ear. The ear module has some resources in src/main/application already but I have a few more to add in a separate artifact with resources classifier and zip type. I can't find any supported way to add these to the ear. i see there is an earSourceDirectory property but that doesn't add a folder like I need, rather that changes the existing resources folder so that will break bringing in the resources at src/main/application which does work...so that property just moves the problem around. This plugin should support flexible ways of bringing in resources...however even if earSourceDirectory added folders instead of replacing them would work for my purposes as I could use maven-dependency-plugin to unzip first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-154) Support PLSQL language
[
https://jira.codehaus.org/browse/MPMD-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-154.
---
Resolution: Won't Fix
Support PLSQL language
--
Key: MPMD-154
URL: https://jira.codehaus.org/browse/MPMD-154
Project: Maven PMD Plugin
Issue Type: Wish
Components: CPD, PMD
Reporter: Stuart Turton
Priority: Minor
Labels: close-pending
Attachments: PldocAST.jj, PldocAST.jjt, plsql-cpd.tgz
DB2, Oracle, EnterpriseDB and TimesTen databases support PLSQL.
Attached is the PLSQL (plus some SQL*Plus) Tokenizer extracted from the PLDoc
project.
StuMacBook:pmd-plsql$ ./cpd_example.sh PLDoc(CPD) version: ${project.version}
LanguageFactory info - attempting to load language plsql
Searching for net.sourceforge.pmd.cpd.PlsqlLanguage using
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PlsqlLanguage using
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PlsqlLanguage using
sun.misc.Launcher.AppClassLoader
LanguageFactory warn - failed to load language Plsql
LanguageFactory info - attempting to load language PLSQL
Searching for net.sourceforge.pmd.cpd.PLSQLLanguage using
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PLSQLLanguage using
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PLSQLLanguage using
sun.misc.Launcher.AppClassLoader
Object(s) like ANONYMOUS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
PLSQLTokenizer: ignoreComments==true
PLSQLTokenizer: ignoreIdentifiers==true
PLSQLTokenizer: ignoreLiterals==true
Object(s) like APEX_PUBLIC_USER. do not exist or system does not have
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like APPQOSSYS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like BI. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like CACHEADM. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like DIP. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like HR_TRIG. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MDDATA. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MGMT_VIEW. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like ORDDATA. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS_AUDIT. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like system.SH do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like SI_INFORMTN_SCHEMA. do not exist or system does not have
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_CSW_ADMIN_USR. do not exist or system does not
have enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_WFS_ADMIN_USR. do not exist or system does not
have enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like TIMESTEN. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like XS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
StuMacBook:pmd-plsql sturton$
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360883#comment-360883
]
Alexander Ashitkin edited comment on SUREFIRE-1132 at 1/7/15 9:01 AM:
--
Ok, after adding some logging it looks like the issues goes to the
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath. In
my case for some reasons generateTestClasspath returned empty classpath. i
suspect the cause is org.apache.maven.project.MavenProject#getArtifacts
implementation issue. Please notice issue which also shows that #getArtifacts
could unxpectedly has null values -MJAR-192.
I have added additionall logging and will continue investigation
thank you
was (Author: alex_ashitkin):
Ok, after adding some logging it looks like the issues goues to the
org.apache.maven.plugin.surefire.AbstractSurefireMojo#generateTestClasspath. In
my case for some reasons generateTestClasspath returned empty classpath. i
suspect the cause is org.apache.maven.project.MavenProject#getArtifacts
implementation issue. Please notice issue which alos shows that getArtifacts
could unxpectedly has null value -MJAR-192.
I have added additionall logging and will continue investigation
thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360889#comment-360889
]
Alexander Ashitkin commented on SUREFIRE-1132:
--
Tibor, generally i have no objections, but i would like to wait for reproducing
case. if i will capture unxepected result in generateTestClasspath then this
one could be closed safely.
Also, in such case i would need to raise an issue to fix
MavenProject#getArtifacts - please advise how to do it properly.
Thank you
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360891#comment-360891
]
Tibor Digana edited comment on SUREFIRE-1132 at 1/7/15 9:39 AM:
@Alexander
I was fixing MavenProject.class in https://github.com/apache/maven/pull/34
We agreed with Jason to wait for immutable objects in maven-core, and not to
push my temporary fix for MavenProject.class.
In case of MavenProject#getArtifacts(), that's Maven Core code. If you are sure
about that, then the bug should belong to https://jira.codehaus.org/browse/MNG
Optionally you may watch the discussions in maven mailinglist
http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
and two discussions related in the sense of concurrency issues
http://maven.40175.n5.nabble.com/Formal-verification-of-thread-correctness-in-maven-core-td5822508.html
http://maven.40175.n5.nabble.com/GitHub-maven-pull-request-Improved-visibility-of-collections-and-variabl-td5821775.html
That's maximum I can help now.
Cheers
was (Author: tibor17):
I was fixing MavenProject.class in https://github.com/apache/maven/pull/34
We agreed with Jason to wait for immutable objects in maven-core, and not to
push my temporary fix for MavenProject.class.
In case of MavenProject#getArtifacts(), that's Maven Core code. If you are sure
about that, then the bug should belong to https://jira.codehaus.org/browse/MNG
Optionally you may watch the discussions in maven mailinglist
http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
and two discussions related in the sense of concurrency issues
http://maven.40175.n5.nabble.com/Formal-verification-of-thread-correctness-in-maven-core-td5822508.html
http://maven.40175.n5.nabble.com/GitHub-maven-pull-request-Improved-visibility-of-collections-and-variabl-td5821775.html
That's maximum I can help now.
Cheers
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, 2.18.1
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/7u65/8u25
Reporter: Alexander Ashitkin
Assignee: Tibor Digana
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360891#comment-360891
]
Tibor Digana commented on SUREFIRE-1132:
I was fixing MavenProject.class in https://github.com/apache/maven/pull/34
We agreed with Jason to wait for immutable objects in maven-core, and not to
push my temporary fix for MavenProject.class.
In case of MavenProject#getArtifacts(), that's Maven Core code. If you are sure
about that, then the bug should belong to https://jira.codehaus.org/browse/MNG
Optionally you may watch the discussions in maven mailinglist
http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
and two discussions related in the sense of concurrency issues
http://maven.40175.n5.nabble.com/Formal-verification-of-thread-correctness-in-maven-core-td5822508.html
http://maven.40175.n5.nabble.com/GitHub-maven-pull-request-Improved-visibility-of-collections-and-variabl-td5821775.html
That's maximum I can help now.
Cheers
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, 2.18.1
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/7u65/8u25
Reporter: Alexander Ashitkin
Assignee: Tibor Digana
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360874#comment-360874
]
Tibor Digana commented on SUREFIRE-1132:
What value was returned from startupConfiguration1.getActualClassName()?
I am still looking for the connection with
org/junit/runner/notification/RunListener class.
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, 2.18.1
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/7u65/8u25
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
forkCount0/forkCount
!--doesnt work in parrallel build. Causes build
failures with error java.io.IOException: Stream Closed--
redirectTestOutputToFilefalse/redirectTestOutputToFile
useManifestOnlyJarfalse/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)
[jira] (MPMD-154) Support PLSQL language
[
https://jira.codehaus.org/browse/MPMD-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360897#comment-360897
]
Stuart Turton commented on MPMD-154:
I know - I think that this was the start of the code changes that ended up in
PMD.
This JIRA item should be closed as fixed/implemented
Support PLSQL language
--
Key: MPMD-154
URL: https://jira.codehaus.org/browse/MPMD-154
Project: Maven PMD Plugin
Issue Type: Wish
Components: CPD, PMD
Reporter: Stuart Turton
Priority: Minor
Labels: close-pending
Attachments: PldocAST.jj, PldocAST.jjt, plsql-cpd.tgz
DB2, Oracle, EnterpriseDB and TimesTen databases support PLSQL.
Attached is the PLSQL (plus some SQL*Plus) Tokenizer extracted from the PLDoc
project.
StuMacBook:pmd-plsql$ ./cpd_example.sh PLDoc(CPD) version: ${project.version}
LanguageFactory info - attempting to load language plsql
Searching for net.sourceforge.pmd.cpd.PlsqlLanguage using
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PlsqlLanguage using
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PlsqlLanguage using
sun.misc.Launcher.AppClassLoader
LanguageFactory warn - failed to load language Plsql
LanguageFactory info - attempting to load language PLSQL
Searching for net.sourceforge.pmd.cpd.PLSQLLanguage using
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PLSQLLanguage using
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PLSQLLanguage using
sun.misc.Launcher.AppClassLoader
Object(s) like ANONYMOUS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
PLSQLTokenizer: ignoreComments==true
PLSQLTokenizer: ignoreIdentifiers==true
PLSQLTokenizer: ignoreLiterals==true
Object(s) like APEX_PUBLIC_USER. do not exist or system does not have
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like APPQOSSYS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like BI. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like CACHEADM. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like DIP. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like HR_TRIG. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MDDATA. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MGMT_VIEW. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like ORDDATA. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS_AUDIT. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like system.SH do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like SI_INFORMTN_SCHEMA. do not exist or system does not have
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_CSW_ADMIN_USR. do not exist or system does not
have enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_WFS_ADMIN_USR. do not exist or system does not
have enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like TIMESTEN. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
Object(s) like XS. do not exist or system does not have enough
permissions (SELECT_CATALOG_ROLE role).
StuMacBook:pmd-plsql sturton$
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
