[jira] [Updated] (MPLUGIN-353) Use Java 7 APIs and language features
[ https://issues.apache.org/jira/browse/MPLUGIN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated MPLUGIN-353: External issue URL: https://github.com/apache/maven-plugin-tools/pull/18 Labels: pull-request-available (was: ) > Use Java 7 APIs and language features > - > > Key: MPLUGIN-353 > URL: https://issues.apache.org/jira/browse/MPLUGIN-353 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: Plugin Plugin >Affects Versions: 3.6.0 >Reporter: Andrew Gaul >Priority: Minor > Labels: pull-request-available > > Use Java 7 features to avoid warnings from error-prone in generated code. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (MPLUGIN-353) Use Java 7 APIs and language features
Andrew Gaul created MPLUGIN-353: --- Summary: Use Java 7 APIs and language features Key: MPLUGIN-353 URL: https://issues.apache.org/jira/browse/MPLUGIN-353 Project: Maven Plugin Tools Issue Type: Improvement Components: Plugin Plugin Affects Versions: 3.6.0 Reporter: Andrew Gaul Use Java 7 features to avoid warnings from error-prone in generated code. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SUREFIRE-1211) surefire-testng runs JUnit tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084986#comment-15084986
]
Andrew Gaul commented on SUREFIRE-1211:
---
Confirmed fixed in Surefire 2.19.1. Thank you for working with me on this!
> surefire-testng runs JUnit tests
>
>
> Key: SUREFIRE-1211
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1211
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19
>Reporter: Andrew Gaul
>Assignee: Tibor Digana
> Fix For: 2.19.1
>
> Attachments: pom.xml
>
>
> When running two test classes, one using JUnit and the other testng
> annotations, I observe surefire-testng running both tests:
> {noformat}
> $ cat src/test/java/JunitTest.java
> import org.junit.Test;
> public final class JunitTest {
> @Test public void junitMethod() throws Exception {}
> }
> $ cat src/test/java/TestngTest.java
> import org.testng.annotations.Test;
> public final class TestngTest {
> @Test public void testngMethod() throws Exception {}
> }
> $ mvn clean test --quiet
> ---
> T E S T S
> ---
> Running JunitTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -
> in JunitTest
> Results :
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> ---
> T E S T S
> ---
> Running TestSuite
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec -
> in TestSuite
> Results :
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Instead it should only run the single testng test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1211) surefire-testng runs JUnit tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070122#comment-15070122
]
Andrew Gaul commented on SUREFIRE-1211:
---
The junit option does not give the output I expect. Consider updating the two
test classes as follows:
{noformat}
$ cat src/test/java/JunitTest.java
import org.junit.Test;
public final class JunitTest {
@Test public void junitMethod() throws Exception {}
@Test public void junitMethod2() throws Exception {}
}
$ cat src/test/java/TestngTest.java
import org.testng.annotations.Test;
public final class TestngTest {
@Test public void testngMethod() throws Exception {}
}
{noformat}
Compare the abridged test output with junit=false:
{noformat}
$ mvn clean test --quiet -Djunit=false
...
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in
JunitTest
...
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.293 sec - in
TestSuite
{noformat}
I expect surefire-testng to only run the testng tests (1 test).
Compare the abridged test output with junit=true:
{noformat}
$ mvn clean test --quiet -Djunit=true
...
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in
JunitTest
...
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.25 sec - in
TestSuite
{noformat}
I expect surefire-testng to run both the JUnit and testng tests (3 tests).
> surefire-testng runs JUnit tests
>
>
> Key: SUREFIRE-1211
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1211
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19
>Reporter: Andrew Gaul
>Assignee: Tibor Digana
> Fix For: 2.19.1
>
> Attachments: pom.xml
>
>
> When running two test classes, one using JUnit and the other testng
> annotations, I observe surefire-testng running both tests:
> {noformat}
> $ cat src/test/java/JunitTest.java
> import org.junit.Test;
> public final class JunitTest {
> @Test public void junitMethod() throws Exception {}
> }
> $ cat src/test/java/TestngTest.java
> import org.testng.annotations.Test;
> public final class TestngTest {
> @Test public void testngMethod() throws Exception {}
> }
> $ mvn clean test --quiet
> ---
> T E S T S
> ---
> Running JunitTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -
> in JunitTest
> Results :
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> ---
> T E S T S
> ---
> Running TestSuite
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec -
> in TestSuite
> Results :
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Instead it should only run the single testng test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1211) surefire-testng runs JUnit tests
Andrew Gaul created SUREFIRE-1211:
-
Summary: surefire-testng runs JUnit tests
Key: SUREFIRE-1211
URL: https://issues.apache.org/jira/browse/SUREFIRE-1211
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.19
Reporter: Andrew Gaul
When running two test classes, one using JUnit and the other testng
annotations, I observe surefire-testng running both tests:
{noformat}
$ cat src/test/java/JunitTest.java
import org.junit.Test;
public final class JunitTest {
@Test public void junitMethod() throws Exception {}
}
$ cat src/test/java/TestngTest.java
import org.testng.annotations.Test;
public final class TestngTest {
@Test public void testngMethod() throws Exception {}
}
$ mvn clean test --quiet
---
T E S T S
---
Running JunitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in
JunitTest
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
---
T E S T S
---
Running TestSuite
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec - in
TestSuite
Results :
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
{noformat}
Instead it should only run the single testng test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1211) surefire-testng runs JUnit tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated SUREFIRE-1211:
--
Attachment: pom.xml
> surefire-testng runs JUnit tests
>
>
> Key: SUREFIRE-1211
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1211
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19
>Reporter: Andrew Gaul
> Attachments: pom.xml
>
>
> When running two test classes, one using JUnit and the other testng
> annotations, I observe surefire-testng running both tests:
> {noformat}
> $ cat src/test/java/JunitTest.java
> import org.junit.Test;
> public final class JunitTest {
> @Test public void junitMethod() throws Exception {}
> }
> $ cat src/test/java/TestngTest.java
> import org.testng.annotations.Test;
> public final class TestngTest {
> @Test public void testngMethod() throws Exception {}
> }
> $ mvn clean test --quiet
> ---
> T E S T S
> ---
> Running JunitTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec -
> in JunitTest
> Results :
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> ---
> T E S T S
> ---
> Running TestSuite
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec -
> in TestSuite
> Results :
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Instead it should only run the single testng test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCHECKSTYLE-296) Issue tracking has stale link
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul closed MCHECKSTYLE-296. --- Verified fixed. Issue tracking has stale link - Key: MCHECKSTYLE-296 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-296 Project: Maven Checkstyle Plugin Issue Type: Improvement Reporter: Andrew Gaul Assignee: Hervé Boutemy Priority: Minor Fix For: 2.16 https://maven.apache.org/plugins/maven-checkstyle-plugin/issue-tracking.html links to: http://jira.codehaus.org/browse/MCHECKSTYLE instead of: https://issues.apache.org/jira/browse/MCHECKSTYLE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHECKSTYLE-296) Issue tracking has stale link
Andrew Gaul created MCHECKSTYLE-296: --- Summary: Issue tracking has stale link Key: MCHECKSTYLE-296 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-296 Project: Maven Checkstyle Plugin Issue Type: Improvement Reporter: Andrew Gaul Priority: Minor https://maven.apache.org/plugins/maven-checkstyle-plugin/issue-tracking.html links to: http://jira.codehaus.org/browse/MCHECKSTYLE instead of: https://issues.apache.org/jira/browse/MCHECKSTYLE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
Andrew Gaul created MCHECKSTYLE-297: --- Summary: pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566277#comment-14566277 ] Andrew Gaul commented on MCHECKSTYLE-297: - Thank you for your feedback! I filed an issue with VersionEye: https://bitbucket.org/versioneye/versioneye/issue/82/license-not-recognized-for-maven pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MASSEMBLY-755) missing whitespace in log message
[
https://jira.codehaus.org/browse/MASSEMBLY-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated MASSEMBLY-755:
--
Priority: Trivial (was: Major)
missing whitespace in log message
-
Key: MASSEMBLY-755
URL: https://jira.codehaus.org/browse/MASSEMBLY-755
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.3
Reporter: Andrew Gaul
Priority: Trivial
Fix For: 2.5.4
Attachments: MASSEMBLY-755.patch
{noformat}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-183) Getting Error creating shaded jar: java.util.jar.Attributes cannot be cast to java.lang.String error when using ManifestResourceTransformer with Maven 3.2.5
[
https://jira.codehaus.org/browse/MSHADE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=365437#comment-365437
]
Andrew Gaul commented on MSHADE-183:
Note that this is still broken with Maven 3.3.1. This is a blocking issue for
me and I have moved back to maven-assembly-plugin.
Getting Error creating shaded jar: java.util.jar.Attributes cannot be cast
to java.lang.String error when using ManifestResourceTransformer with Maven
3.2.5
--
Key: MSHADE-183
URL: https://jira.codehaus.org/browse/MSHADE-183
Project: Maven Shade Plugin
Issue Type: Bug
Reporter: Chris Heisterkamp
Attachments: manifest_resource_transformer_error.diff
If you are using the {{ManifestResourceTransformer}} with empty values in the
configuration you will get a {{Error creating shaded jar:
java.util.jar.Attributes cannot be cast to java.lang.String}} error with
Maven 3.2.5.
Here as an example config that causes the problem
{code:xml}
configuration
transformers
transformer
implementation=org.apache.maven.plugins.shade.resource.ManifestResourceTransformer
manifestEntries
Main-Classcom.mycompany.app.App/Main-Class
Implementation-Build/Implementation-Build
/manifestEntries
/transformer
/transformers
/configuration
{code}
I'm not sure what changed in populating the manifestEntries map but it looks
like the {{manifestEntries.entrySet()}} in {{ManifestResourceTransformer}} is
now getting back {{Attributes}} objects for the {{null}} values instead of
{{null}}. When the transformer calls {{getValue()}} on the {{Attributes}}
object you get the error.
The fix was to make manifestEntries a {{MapString, Object}} instead of
{{MapString, Attributes}}.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-755) missing whitespace in log message
Andrew Gaul created MASSEMBLY-755:
-
Summary: missing whitespace in log message
Key: MASSEMBLY-755
URL: https://jira.codehaus.org/browse/MASSEMBLY-755
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.3
Reporter: Andrew Gaul
Attachments: MASSEMBLY-755.patch
{{noformat}}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{{noformat}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-755) missing whitespace in log message
[
https://jira.codehaus.org/browse/MASSEMBLY-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated MASSEMBLY-755:
--
Description:
{noformat}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{noformat}
was:
{{noformat}}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{{noformat}}
missing whitespace in log message
-
Key: MASSEMBLY-755
URL: https://jira.codehaus.org/browse/MASSEMBLY-755
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.3
Reporter: Andrew Gaul
Attachments: MASSEMBLY-755.patch
{noformat}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-755) missing whitespace in log message
[
https://jira.codehaus.org/browse/MASSEMBLY-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated MASSEMBLY-755:
--
Attachment: MASSEMBLY-755.patch
missing whitespace in log message
-
Key: MASSEMBLY-755
URL: https://jira.codehaus.org/browse/MASSEMBLY-755
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.3
Reporter: Andrew Gaul
Attachments: MASSEMBLY-755.patch
{noformat}
[WARNING] The assembly descriptor contains a filesystem-root relative
reference,which is not cross platform compatible /
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-183) Getting Error creating shaded jar: java.util.jar.Attributes cannot be cast to java.lang.String error when using ManifestResourceTransformer with Maven 3.2.5
[
https://jira.codehaus.org/browse/MSHADE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=363285#comment-363285
]
Andrew Gaul commented on MSHADE-183:
This issue has become more acute with CI services like Travis upgrading to
Maven 3.2.5:
https://travis-ci.org/andrewgaul/s3proxy/builds/50581682
Getting Error creating shaded jar: java.util.jar.Attributes cannot be cast
to java.lang.String error when using ManifestResourceTransformer with Maven
3.2.5
--
Key: MSHADE-183
URL: https://jira.codehaus.org/browse/MSHADE-183
Project: Maven Shade Plugin
Issue Type: Bug
Reporter: Chris Heisterkamp
Attachments: manifest_resource_transformer_error.diff
If you are using the ManifestResourceTransformer with empty values in the
configuration you will get a Error creating shaded jar:
java.util.jar.Attributes cannot be cast to java.lang.String error with Maven
3.2.5.
Here as an example config that causes the problem
{{
configuration
transformers
transformer
implementation=org.apache.maven.plugins.shade.resource.ManifestResourceTransformer
manifestEntries
Main-Classcom.mycompany.app.App/Main-Class
Implementation-Build/Implementation-Build
/manifestEntries
/transformer
/transformers
/configuration
}}
I'm not sure what changed in populating the manifestEntries map but it looks
like the manifestEntries.entrySet() in ManifestResourceTransformer is now
getting back Attributes objects for the null values instead of null. When
the transformer calls getValue() on the Attributes object you get the error.
The fix was to make manifestEntries a MapString, Object instead of
MapString, Attributes.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-261) Upgrade to Checkstyle 6.1.1
[
https://jira.codehaus.org/browse/MCHECKSTYLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361472#comment-361472
]
Andrew Gaul commented on MCHECKSTYLE-261:
-
As a workaround, users can specify the Checkstyle dependency manually:
{noformat}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.13/version
dependencies
dependency
groupIdcom.puppycrawl.tools/groupId
artifactIdcheckstyle/artifactId
version5.9/version
/dependency
/dependencies
/plugin
{noformat}
Upgrade to Checkstyle 6.1.1
---
Key: MCHECKSTYLE-261
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-261
Project: Maven Checkstyle Plugin
Issue Type: Improvement
Affects Versions: 2.14
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
Fix For: 2.15
Upgrade to the latest 6.x version of Checkstyle, which at the time of writing
is 6.1.
Note that this upgrade will make the Checkstyle plugin require Java 6,
because Checkstyle requires Java 6 since version 5.9.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-261) Upgrade to Checkstyle 6.1.1
[
https://jira.codehaus.org/browse/MCHECKSTYLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361471#comment-361471
]
Andrew Gaul commented on MCHECKSTYLE-261:
-
Could you publish a 2.15-SNAPSHOT using Checkstyle 6.1.1? This would allow
users with Java 8 projects with lambdas to use Checkstyle. Presently I see
errors of the form:
{noformat}
/path/SourceFile.java:32:58: unexpected token:
/path/SourceFile.java:34:13: unexpected token: Clock
{noformat}
Upgrade to Checkstyle 6.1.1
---
Key: MCHECKSTYLE-261
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-261
Project: Maven Checkstyle Plugin
Issue Type: Improvement
Affects Versions: 2.14
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
Fix For: 2.15
Upgrade to the latest 6.x version of Checkstyle, which at the time of writing
is 6.1.
Note that this upgrade will make the Checkstyle plugin require Java 6,
because Checkstyle requires Java 6 since version 5.9.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-251) Upgrade to Checkstyle 5.8
Andrew Gaul created MCHECKSTYLE-251: --- Summary: Upgrade to Checkstyle 5.8 Key: MCHECKSTYLE-251 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-251 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.13 Reporter: Andrew Gaul Attachments: checkstyle_5.8.patch This release includes many new violations. Release notes: http://checkstyle.sourceforge.net/releasenotes.html I tested this patch against jclouds without regressions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-230) ConcurrentModificationException in FileResourceLoader.getResource
Andrew Gaul created MCHECKSTYLE-230:
---
Summary: ConcurrentModificationException in
FileResourceLoader.getResource
Key: MCHECKSTYLE-230
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-230
Project: Maven Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.12.1
Reporter: Andrew Gaul
I encountered a ConcurrentModificationException when running:
{noformat}
mvn checkstyle:checkstyle -e -T 4
{noformat}
against the jclouds code base:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle
(default-cli) on project ultradns-ws: Execution default-cli of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle failed.
ConcurrentModificationException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle
(default-cli) on project ultradns-ws: Execution default-cli of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:169)
at
org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:165)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
Caused by: java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
at java.util.ArrayList$Itr.next(ArrayList.java:831)
at
org.codehaus.plexus.resource.loader.FileResourceLoader.getResource(FileResourceLoader.java:56)
at
org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:70)
at
org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:91)
at
org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getOverridingProperties(DefaultCheckstyleExecutor.java:460)
at
org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getConfiguration(DefaultCheckstyleExecutor.java:299)
at
org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:185)
at
org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:488)
at
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:156)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:104)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
... 12 more
{noformat}
The underlying problem appears to be within plexus resources and I have opened
an issue and submitted a possible fix:
http://jira.codehaus.org/browse/PLXCOMP-237
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1028) Unable to run single test (junit)
[
https://jira.codehaus.org/browse/SUREFIRE-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=335726#comment-335726
]
Andrew Gaul edited comment on SUREFIRE-1028 at 11/15/13 11:27 AM:
--
I can trigger these symptoms when setting parallel=classes, similar to
http://jira.codehaus.org/browse/SUREFIRE-827#comment-290928
{noformat}
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.16
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.16
main:
[debug] execute contextualize
[debug] execute contextualize
---
T E S T S
---
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
project commons-lang3: No tests were executed! (Set
-DfailIfNoTests=false to ignore this error.) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{noformat}
was (Author: gaul):
I can trigger these symptoms when setting parallel=classes, similar to
http://jira.codehaus.org/browse/SUREFIRE-827?focusedCommentId=290928page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-290928
{noformat}
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.16
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.16
main:
[debug] execute contextualize
[debug] execute contextualize
---
T E S T S
---
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
project commons-lang3: No tests were executed! (Set
-DfailIfNoTests=false to ignore this error.) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{noformat}
Unable to run single test (junit)
-
Key: SUREFIRE-1028
URL: https://jira.codehaus.org/browse/SUREFIRE-1028
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.16
Reporter: Diwaker Gupta
Priority: Critical
Fix For: 2.17
This is a regression from 2.15. It also looks like Surefire keeps regressing
on this feature (e.g. see SUREFIRE-827) -- are there no unit or integration
tests to prevent such regressions?
With Surefire 2.15
{noformat}
$ mvn test -Dtest=MyTest#testFoo
...
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
With Surefire 2.16
{noformat}
$ mvn test -Dtest=MyTest#testFoo
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1028) Unable to run single test (junit)
[
https://jira.codehaus.org/browse/SUREFIRE-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=335726#comment-335726
]
Andrew Gaul commented on SUREFIRE-1028:
---
I can trigger these symptoms when setting parallel=classes, similar to
http://jira.codehaus.org/browse/SUREFIRE-827?focusedCommentId=290928page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-290928
{noformat}
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.16
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.15
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-DthreadCount=1 -Dsurefire.version=2.16
main:
[debug] execute contextualize
[debug] execute contextualize
---
T E S T S
---
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
project commons-lang3: No tests were executed! (Set
-DfailIfNoTests=false to ignore this error.) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{noformat}
Unable to run single test (junit)
-
Key: SUREFIRE-1028
URL: https://jira.codehaus.org/browse/SUREFIRE-1028
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.16
Reporter: Diwaker Gupta
Priority: Critical
Fix For: 2.17
This is a regression from 2.15. It also looks like Surefire keeps regressing
on this feature (e.g. see SUREFIRE-827) -- are there no unit or integration
tests to prevent such regressions?
With Surefire 2.15
{noformat}
$ mvn test -Dtest=MyTest#testFoo
...
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
With Surefire 2.16
{noformat}
$ mvn test -Dtest=MyTest#testFoo
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-198) Add user property for consoleOutput
[ https://jira.codehaus.org/browse/MCHECKSTYLE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated MCHECKSTYLE-198: Attachment: MCHECKSTYLE-198.patch Add user property for consoleOutput --- Key: MCHECKSTYLE-198 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-198 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.10 Reporter: Andrew Gaul Priority: Minor Attachments: MCHECKSTYLE-198.patch Adding a user property for consoleOutput will allow users to view violations on arbitrary projects, e.g., mvn checkstyle:checkstyle -Dcheckstyle.output.console=true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-198) Add user property for consoleOutput
Andrew Gaul created MCHECKSTYLE-198: --- Summary: Add user property for consoleOutput Key: MCHECKSTYLE-198 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-198 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.10 Reporter: Andrew Gaul Priority: Minor Attachments: MCHECKSTYLE-198.patch Adding a user property for consoleOutput will allow users to view violations on arbitrary projects, e.g., mvn checkstyle:checkstyle -Dcheckstyle.output.console=true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1029) Report suppressed exceptions
Andrew Gaul created SUREFIRE-1029: - Summary: Report suppressed exceptions Key: SUREFIRE-1029 URL: https://jira.codehaus.org/browse/SUREFIRE-1029 Project: Maven Surefire Issue Type: Improvement Components: Maven Surefire Plugin Affects Versions: 2.16 Reporter: Andrew Gaul Attachments: AutoCloseableMain.java, AutoCloseableTest.java Surefire only reports the exception from a try-with-resources body, not any suppressed exceptions from close methods. I see this behavior from the attached AutoCloseableMain.java: Exception in thread main java.io.IOException: from body at AutoCloseableMain.main(AutoCloseableMain.java:9) Suppressed: java.io.IOException: from close at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17) at AutoCloseableMain.main(AutoCloseableMain.java:10) I see a different behavior from the attached AutoCloseableTest.java: java.io.IOException: from body at com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14) Surefire could call Throwable.getSuppressed via reflection to maintain compatibility with earlier versions of Java. Refer to Guava Closer which does something similar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1029) Report suppressed exceptions
[
https://jira.codehaus.org/browse/SUREFIRE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated SUREFIRE-1029:
--
Affects Version/s: 2.15
Report suppressed exceptions
Key: SUREFIRE-1029
URL: https://jira.codehaus.org/browse/SUREFIRE-1029
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.15, 2.16
Reporter: Andrew Gaul
Attachments: AutoCloseableMain.java, AutoCloseableTest.java
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{code}
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
{code}
I see a different behavior from the attached AutoCloseableTest.java:
{code}
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
{code}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which
does something similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1029) Report suppressed exceptions
[
https://jira.codehaus.org/browse/SUREFIRE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated SUREFIRE-1029:
--
Description:
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{code}
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
{code}
I see a different behavior from the attached AutoCloseableTest.java:
{code}
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
{code}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which does
something similar.
was:
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{{
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
}}
I see a different behavior from the attached AutoCloseableTest.java:
{{
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
}}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which does
something similar.
Report suppressed exceptions
Key: SUREFIRE-1029
URL: https://jira.codehaus.org/browse/SUREFIRE-1029
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.16
Reporter: Andrew Gaul
Attachments: AutoCloseableMain.java, AutoCloseableTest.java
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{code}
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
{code}
I see a different behavior from the attached AutoCloseableTest.java:
{code}
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
{code}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which
does something similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1029) Report suppressed exceptions
[
https://jira.codehaus.org/browse/SUREFIRE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated SUREFIRE-1029:
--
Description:
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{{
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
}}
I see a different behavior from the attached AutoCloseableTest.java:
{{
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
}}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which does
something similar.
was:
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
I see a different behavior from the attached AutoCloseableTest.java:
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which does
something similar.
Report suppressed exceptions
Key: SUREFIRE-1029
URL: https://jira.codehaus.org/browse/SUREFIRE-1029
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.16
Reporter: Andrew Gaul
Attachments: AutoCloseableMain.java, AutoCloseableTest.java
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{{
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
}}
I see a different behavior from the attached AutoCloseableTest.java:
{{
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
}}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which
does something similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1030) Remove nested exception wrappers
Andrew Gaul created SUREFIRE-1030: - Summary: Remove nested exception wrappers Key: SUREFIRE-1030 URL: https://jira.codehaus.org/browse/SUREFIRE-1030 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.16 Reporter: Andrew Gaul Priority: Minor Java 1.5 dependency is sufficient to get Throwable.getCause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1030) Remove nested exception wrappers
[ https://jira.codehaus.org/browse/SUREFIRE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332384#comment-332384 ] Andrew Gaul commented on SUREFIRE-1030: --- Pull request: https://github.com/apache/maven-surefire/pull/27 Remove nested exception wrappers Key: SUREFIRE-1030 URL: https://jira.codehaus.org/browse/SUREFIRE-1030 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.16 Reporter: Andrew Gaul Priority: Minor Attachments: SUREFIRE-1030.patch Java 1.5 dependency is sufficient to get Throwable.getCause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1030) Remove nested exception wrappers
[ https://jira.codehaus.org/browse/SUREFIRE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated SUREFIRE-1030: -- Attachment: SUREFIRE-1030.patch Remove nested exception wrappers Key: SUREFIRE-1030 URL: https://jira.codehaus.org/browse/SUREFIRE-1030 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.16 Reporter: Andrew Gaul Priority: Minor Attachments: SUREFIRE-1030.patch Java 1.5 dependency is sufficient to get Throwable.getCause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1029) Report suppressed exceptions
[
https://jira.codehaus.org/browse/SUREFIRE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul closed SUREFIRE-1029.
-
Resolution: Not A Bug
Setting trimStackTrace to false displays any cause or suppressed exceptions.
Unfortunately this emits stacks frames underneath the test method, limiting its
usefulness.
Report suppressed exceptions
Key: SUREFIRE-1029
URL: https://jira.codehaus.org/browse/SUREFIRE-1029
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.15, 2.16
Reporter: Andrew Gaul
Attachments: AutoCloseableMain.java, AutoCloseableTest.java
Surefire only reports the exception from a try-with-resources body, not any
suppressed exceptions from close methods. I see this behavior from the
attached AutoCloseableMain.java:
{code}
Exception in thread main java.io.IOException: from body
at AutoCloseableMain.main(AutoCloseableMain.java:9)
Suppressed: java.io.IOException: from close
at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
at AutoCloseableMain.main(AutoCloseableMain.java:10)
{code}
I see a different behavior from the attached AutoCloseableTest.java:
{code}
java.io.IOException: from body
at
com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
{code}
Surefire could call Throwable.getSuppressed via reflection to maintain
compatibility with earlier versions of Java. Refer to Guava Closer which
does something similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-938) out of memory when logging more messages than heap size
[ https://jira.codehaus.org/browse/SUREFIRE-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325063#comment-325063 ] Andrew Gaul commented on SUREFIRE-938: -- Verified fixed for my use case. Thanks Kristian! out of memory when logging more messages than heap size --- Key: SUREFIRE-938 URL: https://jira.codehaus.org/browse/SUREFIRE-938 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12.4 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Fix For: 2.15 Observed OOM when logging more messages than heap size: Exception in thread ThreadedStreamConsumer java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.init(String.java:215) at java.lang.StringBuilder.toString(StringBuilder.java:430) at org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:225) at org.apache.maven.plugin.surefire.report.TestSetRunListener.wrap(TestSetRunListener.java:230) at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSucceeded(TestSetRunListener.java:161) at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:100) at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-132) Shade does not buffer output, yielding excessive write syscalls
[ https://jira.codehaus.org/browse/MSHADE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323453#comment-323453 ] Andrew Gaul commented on MSHADE-132: Anything blocking merging this patch? Shade does not buffer output, yielding excessive write syscalls --- Key: MSHADE-132 URL: https://jira.codehaus.org/browse/MSHADE-132 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Andrew Gaul Attachments: maven_shade_buffer_output.patch Shade does not buffer output, yielding excessive write syscalls. This slows down mvn package of a local project on a Linux ecryptfs volume from 34s to 3m47s. I attached a patch to address this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-938) out of memory when logging more messages than heap size
[ https://jira.codehaus.org/browse/SUREFIRE-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315893#comment-315893 ] Andrew Gaul commented on SUREFIRE-938: -- Kristian, I opened a pull request which avoids one of the copies: https://github.com/apache/maven-surefire/pull/16 I do not know enough about Surefire to tackle using a file-backed structure at this point. out of memory when logging more messages than heap size --- Key: SUREFIRE-938 URL: https://jira.codehaus.org/browse/SUREFIRE-938 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12.4 Reporter: Andrew Gaul Observed OOM when logging more messages than heap size: Exception in thread ThreadedStreamConsumer java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.init(String.java:215) at java.lang.StringBuilder.toString(StringBuilder.java:430) at org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:225) at org.apache.maven.plugin.surefire.report.TestSetRunListener.wrap(TestSetRunListener.java:230) at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSucceeded(TestSetRunListener.java:161) at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:100) at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-938) out of memory when logging more messages than heap size
Andrew Gaul created SUREFIRE-938: Summary: out of memory when logging more messages than heap size Key: SUREFIRE-938 URL: https://jira.codehaus.org/browse/SUREFIRE-938 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12.4 Reporter: Andrew Gaul Observed OOM when logging more messages than heap size: Exception in thread ThreadedStreamConsumer java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.init(String.java:215) at java.lang.StringBuilder.toString(StringBuilder.java:430) at org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:225) at org.apache.maven.plugin.surefire.report.TestSetRunListener.wrap(TestSetRunListener.java:230) at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSucceeded(TestSetRunListener.java:161) at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:100) at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-132) Shade does not buffer output, yielding excessive write syscalls
Andrew Gaul created MSHADE-132: -- Summary: Shade does not buffer output, yielding excessive write syscalls Key: MSHADE-132 URL: https://jira.codehaus.org/browse/MSHADE-132 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Andrew Gaul Attachments: maven_shade_buffer_output.patch Shade does not buffer output, yielding excessive write syscalls. This slows down mvn package of a local project on a Linux ecryptfs volume from 34s to 3m47s. I attached a patch to address this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=304355#comment-304355 ] Andrew Gaul commented on SUREFIRE-827: -- Verified fixed in r1364394. Thank you for your persistence Kristian. Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Fix For: 2.12.1 Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303106#comment-303106 ] Andrew Gaul commented on SUREFIRE-827: -- Kristian, going back to my example on 06 Feb 2012 with Apache commons-lang 3.1: $ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes -Dsurefire.version=2.11 ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 $ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes -Dsurefire.version=2.12 ... Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 $ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes -Dsurefire.version=2.13-SNAPSHOT ... Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 Tested with maven-surefire-plugin-2.13-20120706.132117-19.jar . Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Fix For: 2.13 Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301745#comment-301745 ] Andrew Gaul commented on SUREFIRE-827: -- This still fails for me with 2.13-20120620.212637-15 running on Ubuntu 12.04. Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Fix For: 2.13 Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294795#comment-294795 ] Andrew Gaul commented on SUREFIRE-827: -- 2.13-SNAPSHOT (2.13-20120228.152625-12) still broken with JUnit. Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[
https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290928#comment-290928
]
Andrew Gaul commented on SUREFIRE-827:
--
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
pre
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
/pre
I cannot speak to Falko's symptoms.
Surefire 2.12 cannot run a single test, regression from 2.11
Key: SUREFIRE-827
URL: https://jira.codehaus.org/browse/SUREFIRE-827
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.12
Environment: Ubuntu 11.10
Reporter: Andrew Gaul
# Surefire 2.11
$ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
# Surefire 2.12
mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
...
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[
https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290928#comment-290928
]
Andrew Gaul edited comment on SUREFIRE-827 at 2/6/12 1:28 PM:
--
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
{noformat}
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
I cannot speak to Falko's symptoms.
was (Author: gaul):
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
pre
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
/pre
I cannot speak to Falko's symptoms.
Surefire 2.12 cannot run a single test, regression from 2.11
Key: SUREFIRE-827
URL: https://jira.codehaus.org/browse/SUREFIRE-827
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.12
Environment: Ubuntu 11.10
Reporter: Andrew Gaul
# Surefire 2.11
$ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
# Surefire 2.12
mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
...
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
Andrew Gaul created SUREFIRE-827: Summary: Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-760) mvn -Dtest=ClassName#methodName does not work with parallel tests
mvn -Dtest=ClassName#methodName does not work with parallel tests - Key: SUREFIRE-760 URL: https://jira.codehaus.org/browse/SUREFIRE-760 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.9 Environment: java version 1.6.0_26 Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) JUnit 4.8.2 Reporter: Andrew Gaul Tested with commons-lang 3.0.1: $ mvn test -Dtest=ImmutablePairTest#testBasic ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 $ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes ... Concurrency config is parallel='classes', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false ... Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-754) unbounded memory use when capturing logs
unbounded memory use when capturing logs Key: SUREFIRE-754 URL: https://jira.codehaus.org/browse/SUREFIRE-754 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.9 Reporter: Andrew Gaul Surefire should dump logs directly to a file instead of buffering in-memory. Exception in thread ThreadedStreamConsumer java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2894) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:117) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:407) at java.lang.StringBuffer.append(StringBuffer.java:241) at org.apache.maven.surefire.report.ConsoleOutputFileReporter.writeMessage(ConsoleOutputFileReporter.java:115) at org.apache.maven.surefire.report.MulticastingReporter.writeMessage(MulticastingReporter.java:101) at org.apache.maven.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:99) at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:132) at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
