[jira] (MINSTALL-73) Add skip parameter
[ https://jira.codehaus.org/browse/MINSTALL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MINSTALL-73: Assignee: Olivier Lamy Add skip parameter -- Key: MINSTALL-73 URL: https://jira.codehaus.org/browse/MINSTALL-73 Project: Maven 2.x Install Plugin Issue Type: Improvement Components: install:install Affects Versions: 2.4 Reporter: Ludwig Magnusson Assignee: Olivier Lamy Attachments: MINSTALL-73.patch, MINSTALL-73-test.patch Hello! The deploy plugin has a skip parameter that if set to true, skips the deploy goal. http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html I was thinking that the install plugin could have the same feature. I have created a patch (wasn't that hard). And I will submit it when i find out what number this task gets =) -- 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] (MINSTALL-73) Add skip parameter
[ https://jira.codehaus.org/browse/MINSTALL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINSTALL-73. Resolution: Fixed Fix Version/s: 2.4 patch applied. Thanks! Add skip parameter -- Key: MINSTALL-73 URL: https://jira.codehaus.org/browse/MINSTALL-73 Project: Maven 2.x Install Plugin Issue Type: Improvement Components: install:install Affects Versions: 2.4 Reporter: Ludwig Magnusson Assignee: Olivier Lamy Fix For: 2.4 Attachments: MINSTALL-73.patch, MINSTALL-73-test.patch Hello! The deploy plugin has a skip parameter that if set to true, skips the deploy goal. http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html I was thinking that the install plugin could have the same feature. I have created a patch (wasn't that hard). And I will submit it when i find out what number this task gets =) -- 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] (MGPG-39) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MGPG-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MGPG-39: Assignee: Olivier Lamy use maven-plugin-tools' java 5 annotations -- Key: MGPG-39 URL: https://jira.codehaus.org/browse/MGPG-39 Project: Maven 2.x and 3.x GPG Plugin Issue Type: Task Affects Versions: 1.4 Reporter: Tony Chemit Assignee: Olivier Lamy Fix For: 1.5 Attachments: MGPG39_2.diff, MGPG39.diff -- 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] (MGPG-39) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MGPG-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MGPG-39: - Fix Version/s: 1.5 use maven-plugin-tools' java 5 annotations -- Key: MGPG-39 URL: https://jira.codehaus.org/browse/MGPG-39 Project: Maven 2.x and 3.x GPG Plugin Issue Type: Task Affects Versions: 1.4 Reporter: Tony Chemit Assignee: Olivier Lamy Fix For: 1.5 Attachments: MGPG39_2.diff, MGPG39.diff -- 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] (MGPG-39) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MGPG-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MGPG-39. Resolution: Fixed applied. Thanks! use maven-plugin-tools' java 5 annotations -- Key: MGPG-39 URL: https://jira.codehaus.org/browse/MGPG-39 Project: Maven 2.x and 3.x GPG Plugin Issue Type: Task Affects Versions: 1.4 Reporter: Tony Chemit Assignee: Olivier Lamy Fix For: 1.5 Attachments: MGPG39_2.diff, MGPG39.diff -- 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=302994#comment-302994
]
Kristian Rosenvold commented on SUREFIRE-827:
-
@Andrew; I am unable to reproduce this on my linux mint installation. Unless
you can supply a mini test-project (maybe modify the one already attached) that
demonstrates this I will close this issue as cannot reproduce.
All the ms-windows users chiming in on this issue should note this has been
fixed for windows.
FWIW I tried this pom:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdSUREFIRE/groupId
artifactIdBUG-827/artifactId
version0.0.1-SNAPSHOT/version
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.10/version
/dependency
/dependencies
propertiessurefire.version2.12/surefire.version/properties
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version${surefire.version}/version
configuration
parallelclasses/parallel
threadCount2/threadCount
/configuration
/plugin
/plugins
/pluginManagement
/build
/project
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-886) [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project
[ https://jira.codehaus.org/browse/SUREFIRE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=302995#comment-302995 ] Kristian Rosenvold commented on SUREFIRE-886: - This is a bit of an interesting issue. The stack trace seems to indicate a severely mismatched state. I suspect that there's something wicked about your includes/excludes that's not being caught by validations, and you run into this really weird place before it all crashes. Can you please run mvn help:effective-pom in the module in question and post the output of the surefire plugin configuration ? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project - Key: SUREFIRE-886 URL: https://jira.codehaus.org/browse/SUREFIRE-886 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12 Environment: Apache Maven 3.0.4 Maven home: /usr/share/maven Java version: 1.6.0_33, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.4 Reporter: Bilal Clarance Priority: Critical Attachments: stack-trace.txt I need to use surefire v2.12, but I get the attached stack trace every time I run that version. If I run v2.10 I do not get the error. I need this version so I can annotate my test classes with @Category and label them as either UnitTests or IntegrationTests. Here's my command: mvn test -Dsurefire.version=2.12 -X Any ideas? -- 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-886) [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project
[ https://jira.codehaus.org/browse/SUREFIRE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilal Clarance updated SUREFIRE-886: Attachment: effective-pom.xml [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project - Key: SUREFIRE-886 URL: https://jira.codehaus.org/browse/SUREFIRE-886 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12 Environment: Apache Maven 3.0.4 Maven home: /usr/share/maven Java version: 1.6.0_33, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.4 Reporter: Bilal Clarance Priority: Critical Attachments: effective-pom.xml, stack-trace.txt I need to use surefire v2.12, but I get the attached stack trace every time I run that version. If I run v2.10 I do not get the error. I need this version so I can annotate my test classes with @Category and label them as either UnitTests or IntegrationTests. Here's my command: mvn test -Dsurefire.version=2.12 -X Any ideas? -- 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-886) [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project
[ https://jira.codehaus.org/browse/SUREFIRE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=302996#comment-302996 ] Bilal Clarance commented on SUREFIRE-886: - Kristian, Please see attached pom from output. Please note that some names have been swapped for security, but only for local artifacts. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project - Key: SUREFIRE-886 URL: https://jira.codehaus.org/browse/SUREFIRE-886 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12 Environment: Apache Maven 3.0.4 Maven home: /usr/share/maven Java version: 1.6.0_33, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.4 Reporter: Bilal Clarance Priority: Critical Attachments: effective-pom.xml, stack-trace.txt I need to use surefire v2.12, but I get the attached stack trace every time I run that version. If I run v2.10 I do not get the error. I need this version so I can annotate my test classes with @Category and label them as either UnitTests or IntegrationTests. Here's my command: mvn test -Dsurefire.version=2.12 -X Any ideas? -- 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-883) Cannot run tests in parallel
[ https://jira.codehaus.org/browse/SUREFIRE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-883. --- Resolution: Fixed Fix Version/s: 2.13 Assignee: Kristian Rosenvold Removed the ClassDemarcatingRunner when running parallel=methods in r1358826 Cannot run tests in parallel Key: SUREFIRE-883 URL: https://jira.codehaus.org/browse/SUREFIRE-883 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Reporter: Steve Stogner Assignee: Kristian Rosenvold Priority: Minor Fix For: 2.13 Revision 1228960 seems to break parallel tests. See ConfigurableParallelComputer.java. before: Call to super.getRunner returns a ParentRunner that ConfigurableParallelComputer.getRunner passes directly to parallelize after: Call to super.getRunner returns a ParentRunner, but ConfigurableParallelComputer.getRunner wraps that ParentRunner in a ClassDemarcatingRunner which it then passes to parallelize problem: Parallelize calls setScheduler (and therefore parallelizes the tests) only for ParentRunners. Since the ParentRunner of interest is wrapped inside the ClassDemarcatingRunner, which is not a ParentRunner, parallelize does not call setScheduler. -- 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-873) NPE in DefaultArtifactResolver.java:312
[
https://jira.codehaus.org/browse/SUREFIRE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-873.
---
Resolution: Cannot Reproduce
Assignee: Kristian Rosenvold
Cant reproduce, unknown version
NPE in DefaultArtifactResolver.java:312
---
Key: SUREFIRE-873
URL: https://jira.codehaus.org/browse/SUREFIRE-873
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.7.2, 2.9, 2.10, 2.12
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 11:44:56+0300)
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
Default locale: ru_RU, platform encoding: UTF-8
OS name: linux, version: 2.6.32-30-generic, arch: i386, family: unix
Reporter: Rodionov Andrey
Assignee: Kristian Rosenvold
{code}
Caused by: java.lang.NullPointerException
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:312)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:293)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:271)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:256)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.resolveArtifact(AbstractSurefireMojo.java:779)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.addArtifact(AbstractSurefireMojo.java:787)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.createStartupConfiguration(AbstractSurefireMojo.java:349)
{code}
--
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-865) surefire 2.12 with parallel=methods does not execute junit 4.7+ tests in parallel
[ https://jira.codehaus.org/browse/SUREFIRE-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-865. --- Resolution: Fixed Fix Version/s: 2.13 Assignee: Kristian Rosenvold Fixed with the ClassDemarcatingRunner issue surefire 2.12 with parallel=methods does not execute junit 4.7+ tests in parallel - Key: SUREFIRE-865 URL: https://jira.codehaus.org/browse/SUREFIRE-865 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Environment: Maven 2.2.1 and 3.0.4, JDK6, JUnit 4.10 Reporter: Neil Hartner Assignee: Kristian Rosenvold Fix For: 2.13 Attachments: surefire-parallel-junit.zip parallel=methods with junit does not appear to parallelize junit test execution in surefire 2.12 or 2.13-SNAPSHOT. parallel=classes works with 2.12, but parallel=methods only works for me in earlier versions of surefire like 2.10 and 2.11. I saw an earlier bug related to TestSuite classes but my tests are not using @Test. I have attached a very simple maven project that demonstrates this issue. It has 2 test classes with 2 tests each where each test calls Thread.sleep() for 4-8 seconds. Here are a few build commands to reproduce the bug: First run: mvn test -Dsurefire-version=2.11 -Dparallel=methods Notice that in 2.11 the tests execute in two threads and in parallel. Total execution time on my box was 15s. Then run: mvn test -Dsurefire-version=2.12 -Dparallel=methods Notice that in 2.12 the tests execute in the same main thread. Total execution time on my box was 26s. Finally run: mvn test -Dsurefire-version=2.12 -Dparallel=classes Notice that parallel=classes does correctly execute tests in two threads and in parallel. Total execution time on my box was 17s. --- Here is output from my machine when running these commands... Run: mvn test -Dsurefire-version=2.11 -Dparallel=methods OUTPUT: Concurrency config is parallel='methods', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false Running com.overstock.BarTest Fri May 11 11:26:34 MDT 2012: BarTest calling sleep(5) in thread pool-1-thread-2 Fri May 11 11:26:34 MDT 2012: BarTest calling sleep(4) in thread pool-1-thread-1 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.033 sec Running com.overstock.FooTest Fri May 11 11:26:39 MDT 2012: FooTest calling sleep(7) in thread pool-1-thread-3 Fri May 11 11:26:39 MDT 2012: FooTest calling sleep(8) in thread pool-1-thread-4 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.008 sec Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 15 seconds Run: mvn test -Dsurefire-version=2.12 -Dparallel=methods OUTPUT: Concurrency config is parallel='methods', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false Running com.overstock.BarTest Fri May 11 11:25:53 MDT 2012: BarTest calling sleep(4) in thread main Fri May 11 11:25:58 MDT 2012: BarTest calling sleep(5) in thread main Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.017 sec Running com.overstock.FooTest Fri May 11 11:26:03 MDT 2012: FooTest calling sleep(7) in thread main Fri May 11 11:26:10 MDT 2012: FooTest calling sleep(8) in thread main Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.003 sec Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 26 seconds Run: mvn test -Dsurefire-version=2.12 -Dparallel=classes OUTPUT: Concurrency config is parallel='classes', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false Running com.overstock.BarTest Fri May 11 11:27:38 MDT 2012: BarTest calling sleep(4) in thread pool-1-thread-1 Fri May 11 11:27:42 MDT 2012: BarTest calling sleep(5) in thread pool-1-thread-1 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.016 sec Running com.overstock.FooTest Fri May 11 11:27:38 MDT 2012: FooTest calling sleep(7) in thread pool-1-thread-2 Fri May 11 11:27:45 MDT 2012: FooTest calling sleep(8) in thread pool-1-thread-2 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.016 sec Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO]
[jira] (SUREFIRE-870) Error occurred in starting fork shouldn't be reported for all forks with non-zero exit codes
[ https://jira.codehaus.org/browse/SUREFIRE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-870. --- Resolution: Fixed Assignee: Kristian Rosenvold Fixed in r1358827 Error occurred in starting fork shouldn't be reported for all forks with non-zero exit codes -- Key: SUREFIRE-870 URL: https://jira.codehaus.org/browse/SUREFIRE-870 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.12 Reporter: Andrew Bayer Assignee: Kristian Rosenvold If a forked test has a non-zero exit code for any reason, it's reported by Surefire as Error occurred in starting fork. It's distinctly possible for a forked test to have a non-zero exit code for reasons other than problems starting the fork - i.e., a bad test that as a System.exit(1) in it, etc. The error should either be more general, or more specific tracing of the problem should be done. -- 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-871) Output of forked tests with non-zero exit code not retained
[ https://jira.codehaus.org/browse/SUREFIRE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-871: Fix Version/s: 2.13 Output of forked tests with non-zero exit code not retained --- Key: SUREFIRE-871 URL: https://jira.codehaus.org/browse/SUREFIRE-871 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.12 Reporter: Andrew Bayer Assignee: Kristian Rosenvold Fix For: 2.13 If a forked test has a non-zero exit code, its output (stdout/err) is not retained anywhere, so it's not possible to see why the test errored/failed/whatever. -- 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-871) Output of forked tests with non-zero exit code not retained
[ https://jira.codehaus.org/browse/SUREFIRE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303001#comment-303001 ] Kristian Rosenvold edited comment on SUREFIRE-871 at 7/8/12 3:23 PM: - This should be fixed, it was related to the same logic that gave the bad error message. Feel free to reopen if this is not the case was (Author: krosenvold): This should be fixed, it was related to the same logic that gave the bad error message. Output of forked tests with non-zero exit code not retained --- Key: SUREFIRE-871 URL: https://jira.codehaus.org/browse/SUREFIRE-871 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.12 Reporter: Andrew Bayer Assignee: Kristian Rosenvold Fix For: 2.13 If a forked test has a non-zero exit code, its output (stdout/err) is not retained anywhere, so it's not possible to see why the test errored/failed/whatever. -- 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-871) Output of forked tests with non-zero exit code not retained
[ https://jira.codehaus.org/browse/SUREFIRE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-871. --- Resolution: Fixed Assignee: Kristian Rosenvold This should be fixed, it was related to the same logic that gave the bad error message. Output of forked tests with non-zero exit code not retained --- Key: SUREFIRE-871 URL: https://jira.codehaus.org/browse/SUREFIRE-871 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.12 Reporter: Andrew Bayer Assignee: Kristian Rosenvold If a forked test has a non-zero exit code, its output (stdout/err) is not retained anywhere, so it's not possible to see why the test errored/failed/whatever. -- 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-863) NPE in ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303002#comment-303002 ] Kristian Rosenvold commented on SUREFIRE-863: - I think this patch wont work, since I had to remove some use of the ClassDemarcatingRunner NPE in ConcurrentReporterManager Key: SUREFIRE-863 URL: https://jira.codehaus.org/browse/SUREFIRE-863 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Reporter: Mark Struberg Attachments: SUREFIRE-863.patch I have a wird NPE in surefire with one of my projects: Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getTestSet(ConcurrentReporterManager.java:157) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getOrCreateTestMethod(ConcurrentReporterManager.java:127) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testError(ConcurrentReporterManager.java:83) at org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFailure(JUnit4RunListener.java:110) at org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:100) -- 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-863) NPE in ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303002#comment-303002 ] Kristian Rosenvold edited comment on SUREFIRE-863 at 7/8/12 3:26 PM: - I think this patch wont work, since I had to remove some use of the ClassDemarcatingRunner. Looking at the original code, it probably got worse too. was (Author: krosenvold): I think this patch wont work, since I had to remove some use of the ClassDemarcatingRunner NPE in ConcurrentReporterManager Key: SUREFIRE-863 URL: https://jira.codehaus.org/browse/SUREFIRE-863 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Reporter: Mark Struberg Attachments: SUREFIRE-863.patch I have a wird NPE in surefire with one of my projects: Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getTestSet(ConcurrentReporterManager.java:157) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getOrCreateTestMethod(ConcurrentReporterManager.java:127) at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testError(ConcurrentReporterManager.java:83) at org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFailure(JUnit4RunListener.java:110) at org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:100) -- 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] (MENFORCER-132) Add missing rules to standard rules page and reorder them
[
https://jira.codehaus.org/browse/MENFORCER-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303004#comment-303004
]
Barrie Treloar commented on MENFORCER-132:
--
Fixed documentation in
[r1358882|http://svn.apache.org/viewvc?rev=1358882view=rev]
Add missing rules to standard rules page and reorder them
-
Key: MENFORCER-132
URL: https://jira.codehaus.org/browse/MENFORCER-132
Project: Maven 2.x Enforcer Plugin
Issue Type: Task
Components: Standard Rules
Affects Versions: 1.1
Reporter: Robert Scholte
Assignee: Robert Scholte
Priority: Minor
Fix For: 1.2
The {{RequireNoRepositories}} is quite an important rule, which is not listed
on the [Standard
Rules|http://maven.apache.org/enforcer/enforcer-rules/index.html]-page, just
like the {{RequireActiveProfile}} rule.
While we're here, let's apply some order to these rules.
--
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
