[jira] Commented: (MREACTOR-15) mvn reactor:make-scm-changes doesn't work in windows with subversion
[ http://jira.codehaus.org/browse/MREACTOR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258311#action_258311 ] Christoph Kutzinski commented on MREACTOR-15: - I've got the same problem on Linux + SVN I could fix it by specifiying the new dependencies for the plugin as in the patch. Could please someone release a new version with the fix as probably a lot of people are affected by this problem? > mvn reactor:make-scm-changes doesn't work in windows with subversion > > > Key: MREACTOR-15 > URL: http://jira.codehaus.org/browse/MREACTOR-15 > Project: Maven 2.x Reactor Plugin > Issue Type: Bug >Affects Versions: 1.0 > Environment: windows xp, subversion 1.6.2 command line >Reporter: Roger Pack >Priority: Minor > Attachments: patch.txt > > > In my project, if I update a file, call it > root > /updatemigrationdb > pom.xml > If I update pom.xml and have uncommitted changes there, in linux I get > [INFO] Reactor Summary: > [INFO] > > [INFO] Migration updatemigrationdb ... SUCCESS > [3.741s] > [INFO] Migration TapeWriter .. SUCCESS > [4.361s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Mon Oct 19 17:22:49 MDT 2009 > [INFO] Final Memory: 43M/731M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > however, on windows I get > C:\dev\trunk>mvn reactor:make-scm-changes > ... > [INFO] Executing: cmd.exe /X /C "svn --non-interactive status" > [INFO] Working directory: C:\dev\trunk > [INFO] Going to make dependents for: > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] No folders matched: > ... > The output of said command line is > C:\dev\trunk>cmd /X /C "svn --non-interactive status" > M pom.xml > M updatemigrationdb\pom.xml > (i.e. ? cmd.exe\nM pom.xml\nM updatemigrationdb\\pom.xml\n") > Thanks! > -r -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5032) How to build visual basic 6.0 project in Maven
[ http://jira.codehaus.org/browse/MNG-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5032. -- Resolution: Not A Bug Assignee: Benjamin Bentmann Repeating the introduction page to this issue tracking project: The issue tracker is not a support forum. Questions regarding the usage of Maven belong to the [user list|http://maven.apache.org/mail-lists.html]. > How to build visual basic 6.0 project in Maven > -- > > Key: MNG-5032 > URL: http://jira.codehaus.org/browse/MNG-5032 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 2.2.1 > Environment: i am using Maven 2.2.1 version and JDK1.6 >Reporter: rajamohan >Assignee: Benjamin Bentmann >Priority: Blocker > > we are moving ant script to maven script based on our road map. we have > script for Visual basic6.0 application, need to convert ant script to maven > script for that we are looking plug-in to build vb6.0 application. > Please help me to resolve issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-707) NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on test class)
[ http://jira.codehaus.org/browse/SUREFIRE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258331#action_258331 ] Kristian Rosenvold commented on SUREFIRE-707: - Also here I suspect forkedProcessTimeoutInSeconds set to something non-zero when this happens ? Those runaway threads seem to indicate forkedProcessTimeoutInSeconds is not safe to use in parallel mode at the moment. Although the issue is actually present in all the providers, it only really has consequences in parallel. > NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on > test class) > > > Key: SUREFIRE-707 > URL: http://jira.codehaus.org/browse/SUREFIRE-707 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 > Environment: $ mvn -version > Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_22, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix" >Reporter: Mark Renouf > > Captured using a custom RunListener, tracing to a file: > 2011-02-28-13:30:02.137 TEST_FAILED - Test mechanism: null > java.lang.NullPointerException > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testSkipped(ConcurrentReporterManager.java:107) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testIgnored(JUnit4RunListener.java:68) > at > org.junit.runner.notification.RunNotifier$6.notifyListener(RunNotifier.java:130) > at > org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41) > at > org.junit.runner.notification.RunNotifier.fireTestIgnored(RunNotifier.java:127) > at > org.junit.internal.builders.IgnoredClassRunner.run(IgnoredClassRunner.java:19) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > org.apache.maven.surefire.junitcore.ConfigurableParallelComputer$AsynchronousRunner$1.call(ConfigurableParallelComputer.java:185) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-566) Bump to Doxia 1.1.1
[ http://jira.codehaus.org/browse/SUREFIRE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed SUREFIRE-566. -- Resolution: Fixed Fix Version/s: 2.7.3 Assignee: Lukas Theussl Done in [r1076592|http://svn.apache.org/viewvc?view=revision&revision=1076592]. Please review, I haven't tested too thoroughly. > Bump to Doxia 1.1.1 > --- > > Key: SUREFIRE-566 > URL: http://jira.codehaus.org/browse/SUREFIRE-566 > Project: Maven Surefire > Issue Type: Task > Components: Maven Surefire Report Plugin >Affects Versions: 2.4.3 >Reporter: Vincent Siveton >Assignee: Lukas Theussl > Fix For: 2.7.3 > > Attachments: surefire566VersionUpdates.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-711) OutOfMemoryError while building multi module projects
OutOfMemoryError while building multi module projects - Key: SUREFIRE-711 URL: http://jira.codehaus.org/browse/SUREFIRE-711 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.2 Environment: Win 7 32bit Reporter: Christian Moser Priority: Critical Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG We're getting out of memory errors since we've updated to surefire 2.7.2 from 2.6. Please check the attached jvisualvm pics they show the same build execution with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be interesting. it seems like 2.7.2 is not unloading classes after processing. We found out that if we skip tests with -DskipTests=true, the exception won't occur. The build consists of several multi module projects. ..\..\BaseSys\trunk (multimodule) ..\..\MagIC\trunk (multimodule) ..\..\StabNet\trunk (multimodule) ..\..\tiamo\trunk (multimodule) ..\..\TiBase\trunk (multimodule) ..\..\VIVA\trunk (multimodule) [ERROR] Java heap space -> [Help 1]---Exception in thread "main" jav lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2786) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) at java.io.PrintStream.write(PrintStream.java:430) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258339#action_258339 ] Christian Moser commented on SUREFIRE-711: -- maven version: 3.0.1 or 3.0.2 > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258340#action_258340 ] Christian Moser edited comment on SUREFIRE-711 at 3/3/11 6:28 AM: -- delete me was (Author: onmomo): mvn call: mvn -f all-pom.xml -DloadTestModules=true -Dtest=skip -Denforcer.skip=true clean install -U -DfailIfNoTests=false > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258339#action_258339 ] Christian Moser edited comment on SUREFIRE-711 at 3/3/11 6:28 AM: -- maven version: 3.0.1 or 3.0.2 mvn call: mvn -f all-pom.xml -DloadTestModules=true -Dtest=skip -Denforcer.skip=true clean install -U -DfailIfNoTests=false was (Author: onmomo): maven version: 3.0.1 or 3.0.2 > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258340#action_258340 ] Christian Moser commented on SUREFIRE-711: -- mvn call: mvn -f all-pom.xml -DloadTestModules=true -Dtest=skip -Denforcer.skip=true clean install -U -DfailIfNoTests=false > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5033) Allow to inline collection/array items within plugin configuration
Allow to inline collection/array items within plugin configuration
--
Key: MNG-5033
URL: http://jira.codehaus.org/browse/MNG-5033
Project: Maven 2 & 3
Issue Type: Improvement
Components: Plugins and Lifecycle
Reporter: Benjamin Bentmann
Priority: Minor
The need to wrap collection/array elements into a container element is
occasionally frustrating to users (XML verbosity). Within plugin configuration,
this can be achieved without a new model format, e.g.
{code:xml
src/demo
Foo*
Bar*
*Bad
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5033) Allow to inline collection/array items within plugin configuration
[
http://jira.codehaus.org/browse/MNG-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-5033:
---
Description:
The need to wrap collection/array elements into a container element is
occasionally frustrating to users (XML verbosity). Within plugin configuration,
this can be achieved without a new model format, e.g.
{code:xml}
src/demo
Foo*
Bar*
*Bad
{code}
was:
The need to wrap collection/array elements into a container element is
occasionally frustrating to users (XML verbosity). Within plugin configuration,
this can be achieved without a new model format, e.g.
{code:xml
src/demo
Foo*
Bar*
*Bad
{code}
> Allow to inline collection/array items within plugin configuration
> --
>
> Key: MNG-5033
> URL: http://jira.codehaus.org/browse/MNG-5033
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
>Reporter: Benjamin Bentmann
>Priority: Minor
>
> The need to wrap collection/array elements into a container element is
> occasionally frustrating to users (XML verbosity). Within plugin
> configuration, this can be achieved without a new model format, e.g.
> {code:xml}
>
> src/demo
> Foo*
> Bar*
> *Bad
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5033) Allow to inline collection/array items within plugin configuration
[
http://jira.codehaus.org/browse/MNG-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5033.
--
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
Plugin authors that wish to enable this kind of configuration can equip their
parameter beans with an adder like this:
{code:java}
public class Fileset
{
private List includes = new ArrayList();
public void addInclude( String include )
{
includes.add( include );
}
...
}
{code}
> Allow to inline collection/array items within plugin configuration
> --
>
> Key: MNG-5033
> URL: http://jira.codehaus.org/browse/MNG-5033
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.3
>
>
> The need to wrap collection/array elements into a container element is
> occasionally frustrating to users (XML verbosity). Within plugin
> configuration, this can be achieved without a new model format, e.g.
> {code:xml}
>
> src/demo
> Foo*
> Bar*
> *Bad
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5030) Provide a way to get a raw XML for plugin to read
[
http://jira.codehaus.org/browse/MNG-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258342#action_258342
]
Benjamin Bentmann commented on MNG-5030:
bq. In my plugins I don't like wrapping single tag with a plural option:
This reminded to fill/track MNG-5033.
> Provide a way to get a raw XML for plugin to read
> -
>
> Key: MNG-5030
> URL: http://jira.codehaus.org/browse/MNG-5030
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Plugin API
>Affects Versions: 3.0.2
>Reporter: Evgeny Goldin
>
> As a plugin author I may need to read its *{{}}* slightly
> different than Maven does it. It would be very nice to get a raw XML as an
> alternative to standard fields injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-711: Comment: was deleted (was: delete me) > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258349#action_258349 ] Kristian Rosenvold commented on SUREFIRE-711: - Are you certain there's no 2.6 left in there somewhere ? The stack trace in the log seems to be *exactly* the bug that was fixed in SUREFIRE-495. I am not sure I am reading the log files correctly either, but it would seem like the stacktrace is coming from some kind of forked process invocation. > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-41) Add a list of available language in site plugin
[
http://jira.codehaus.org/browse/MSITE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258350#action_258350
]
Lukas Theussl commented on MSITE-41:
This will have to be revisited after MSITE-322. Different language sites are
now deployed into their own tree like eg
{noformat}
main
index.html
submodule/index.html
fr/index.html
fr/submodule/index.html
{noformat}
Before it was:
{noformat}
main
index.html
fr/index.html
submodule/index.html
submodule/fr/index.html
{noformat}
so switching between language sites, the relative links have changed.
> Add a list of available language in site plugin
> ---
>
> Key: MSITE-41
> URL: http://jira.codehaus.org/browse/MSITE-41
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: New Feature
> Components: internationalization
>Reporter: Vincent Siveton
> Fix For: 2.3
>
> Attachments: language_menu.jpg, language_menu.jpg, language_menu.jpg,
> language_menu_as_select.jpg, MSITE-41-doxia-sitetools.patch,
> MSITE-41-maven-site-plugin.patch
>
>
> Please see the attached screenshots
> This preference menu could be a list of links or a tag.
> The site descriptor needs to be updated:
> * for , by adding asSelect attribute in the menu element.
> * for links list, by adding nostrong attribute in the menu element (to not
> display as strong the current language and the current page)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5030) Provide a way to get a raw XML for plugin to read
[
http://jira.codehaus.org/browse/MNG-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258353#action_258353
]
Evgeny Goldin commented on MNG-5030:
Good, thanks! But it only works with maven 3, right? If I have an adder - Maven
2 will ignore it?
> Provide a way to get a raw XML for plugin to read
> -
>
> Key: MNG-5030
> URL: http://jira.codehaus.org/browse/MNG-5030
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Plugin API
>Affects Versions: 3.0.2
>Reporter: Evgeny Goldin
>
> As a plugin author I may need to read its *{{}}* slightly
> different than Maven does it. It would be very nice to get a raw XML as an
> alternative to standard fields injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5030) Provide a way to get a raw XML for plugin to read
[
http://jira.codehaus.org/browse/MNG-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258356#action_258356
]
Benjamin Bentmann commented on MNG-5030:
Yes, this is 3.0.3+ only, older versions will not look for the adder.
> Provide a way to get a raw XML for plugin to read
> -
>
> Key: MNG-5030
> URL: http://jira.codehaus.org/browse/MNG-5030
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Plugin API
>Affects Versions: 3.0.2
>Reporter: Evgeny Goldin
>
> As a plugin author I may need to read its *{{}}* slightly
> different than Maven does it. It would be very nice to get a raw XML as an
> alternative to standard fields injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258361#action_258361 ] Christian Moser commented on SUREFIRE-711: -- There's only one surefire configuration available in our build system. Perhaps, SUREFIRE-495 was only fixed for test-ng? With 2.6, we are able to sucessfully execute the build. We are even able to execute all test classes (~1400) in forked VM's without OutOfMemoryError's. With 2.7.2, the error occurs while executing an ant-run process, test's aren't executed at all, they are disabled. > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Priority: Critical > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-705) Setting both "forkedProcessTimeoutInSeconds" and "parallel" fails with an exception
[
http://jira.codehaus.org/browse/SUREFIRE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-705.
---
Resolution: Fixed
Fix Version/s: 2.8
Assignee: Kristian Rosenvold
Fixed in r1076367
> Setting both "forkedProcessTimeoutInSeconds" and "parallel" fails with an
> exception
> ---
>
> Key: SUREFIRE-705
> URL: http://jira.codehaus.org/browse/SUREFIRE-705
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, process forking
>Affects Versions: 2.7.2
> Environment: OS X
>Reporter: Jari Aarniala
>Assignee: Kristian Rosenvold
> Fix For: 2.8
>
>
> Setting forkedProcessTimeoutInSeconds to a non-zero value and having parallel
> set throws an exception. Is this not supported?
> Reproducible with a minimal pom.xml:
> {code}
>
> 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";>
> 4.0.0
> my.groupId
> my-archetype-id
> 1.0-SNAPSHOT
> jar
>
>
> junit
> junit
> 4.8.2
> test
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.7.2
>
> 1
> classes
> 10
>
>
>
>
>
> {code}
> Stack trace:
> {code}
> ---
> T E S T S
> ---
> Concurrency config is parallel='classes', perCoreThreadCount=true,
> threadCount=10, useUnlimitedThreads=false
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> ... 4 more
> Caused by: java.lang.IllegalStateException: Task already scheduled or
> cancelled
> at java.util.Timer.sched(Timer.java:358)
> at java.util.Timer.schedule(Timer.java:170)
> at
> org.apache.maven.surefire.report.ReporterManagerFactory.startTimer(ReporterManagerFactory.java:206)
> at
> org.apache.maven.surefire.report.ReporterManagerFactory.createReporter(ReporterManagerFactory.java:105)
> at
> org.apache.maven.surefire.junitcore.ConcurrentReporterManager.(ConcurrentReporterManager.java:64)
> at
> org.apache.maven.surefire.junitcore.ClassesParallelRunListener.(ClassesParallelRunListener.java:38)
> at
> org.apache.maven.surefire.junitcore.ConcurrentReporterManager.createInstance(ConcurrentReporterManager.java:209)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:101)
> ... 9 more
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-692) Wrong link to API
[ http://jira.codehaus.org/browse/SUREFIRE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-692. --- Resolution: Fixed Fix Version/s: 2.8 Assignee: Kristian Rosenvold Fixed in r1076671. Thanks for the patch. We will try to make 1 site for surefire/failsafe soon. > Wrong link to API > - > > Key: SUREFIRE-692 > URL: http://jira.codehaus.org/browse/SUREFIRE-692 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 2.7.2 > Environment: All >Reporter: Karl Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.8 > > Attachments: SUREFIRE-692.patch > > > The link API found on maven-failsafe-plugin > (http://maven.apache.org/plugins/maven-failsafe-plugin/) site is wrong it's > pointing to http://maven.apache.org/plugins/maven-failsafe-plugin/api.html > which produces a "Page not found" ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-702) Introduce a ClasspathPropertiesMapper class
[ http://jira.codehaus.org/browse/SUREFIRE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-702. --- Resolution: Fixed Fix Version/s: 2.8 Assignee: Kristian Rosenvold Thanks for the patch! Fixed in r1076672, applied with modifications. > Introduce a ClasspathPropertiesMapper class > --- > > Key: SUREFIRE-702 > URL: http://jira.codehaus.org/browse/SUREFIRE-702 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.7.2 >Reporter: Stefan Birkner >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.8 > > Attachments: ClasspathPropertiesMapper.patch > > > I created a class named ClasspathPropertiesMapper. This class handles writing > Classpath to Properties and restoring it. Additionally I moved the logic of > storing and restoring a ClasspathConfiguration to the class itself. As a > result some of the BooterConstants are now hidden within > ClasspathConfiguration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-663) Null error when project is too close to root
Null error when project is too close to root Key: MRELEASE-663 URL: http://jira.codehaus.org/browse/MRELEASE-663 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Environment: Maven 2.2.1, Windows XP SP3 Reporter: Brent Smith Priority: Minor Co-worker ran into issues where if he had checked out his project directly in his root dir C:\ (top pom ending up in C:\project\pom.xml) and ran the release:prepare goal he would rather quickly recieve this error: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.shared.release.util.ReleaseUtil.getBaseWorkingDirect oryParentCount(ReleaseUtil.java:233) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.tran slateScm(RewritePomsForReleasePhase.java:109) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.tran sformScm(RewritePomsForReleasePhase.java:62) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transf ormDocument(AbstractRewritePomsPhase.java:303) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transf ormProject(AbstractRewritePomsPhase.java:208) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transf orm(AbstractRewritePomsPhase.java:114) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execut e(AbstractRewritePomsPhase.java:97) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default ReleaseManager.java:203) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default ReleaseManager.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(Default ReleaseManager.java:103) at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(Pr epareReleaseMojo.java:211) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe leaseMojo.java:181) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:694) I looked into it and eventually had him add a "buffer directory" so his top pom was resting in C:\workspace\project\pom.xml and following this move it built properly. Not sure if there is a real requirement to have this buffer directory, but a better error message would be helpful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-227) Add document properties to the velocity context
Add document properties to the velocity context --- Key: MCHANGES-227 URL: http://jira.codehaus.org/browse/MCHANGES-227 Project: Maven 2.x Changes Plugin Issue Type: New Feature Components: announcement Affects Versions: 2.4 Reporter: SebbASF The plugin currently makes almost all of the changes.xml content available to custom templates. However the document properties are not currently made available as far as I can tell. It would sometimes be useful to be able to pass in variable content from changes.xml, rather than from announceParameters in the POM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258420#action_258420 ] Kristian Rosenvold commented on SUREFIRE-690: - Plexus utils 2.0.7 will be appearing in maven central in a few hours. Adding this to surefire should solve this issue; maven-surefire-plugin org.codehaus.plexus plexus-utils 2.0.7 Please report back on the effects of this. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > Fix For: 2.7.3 > > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-710) ConcurrentModificationException in ConcurrentReporterManager
[ http://jira.codehaus.org/browse/SUREFIRE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258421#action_258421 ] Kristian Rosenvold commented on SUREFIRE-710: - Plexus utils 2.0.7 will be appearing in maven central in a few hours. Adding this to surefire should solve this issue; maven-surefire-plugin org.codehaus.plexus plexus-utils 2.0.7 Please report back on the effects of this. > ConcurrentModificationException in ConcurrentReporterManager > > > Key: SUREFIRE-710 > URL: http://jira.codehaus.org/browse/SUREFIRE-710 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 > Environment: $ mvn -version > Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_22, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix" >Reporter: Mark Renouf > > Captured using custom RunListener, tracing to a file: > 2011-02-28-17:05:30.377 TEST_FAILED - Test mechanism: > java.util.ConcurrentModificationException > 2011-02-28-17:05:30.378 java.lang.RuntimeException: > java.util.ConcurrentModificationException > at org.apache.maven.surefire.junitcore.TestSet.replay(TestSet.java:91) > at > org.apache.maven.surefire.junitcore.TestSet.setAllScheduled(TestSet.java:134) > at > org.apache.maven.surefire.junitcore.ClassesParallelRunListener.checkIfTestSetCanBeReported(ClassesParallelRunListener.java:47) > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testStarting(ConcurrentReporterManager.java:123) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testStarted(JUnit4RunListener.java:79) > at > org.junit.runner.notification.RunNotifier$3.notifyListener(RunNotifier.java:87) > at > org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41) > at > org.junit.runner.notification.RunNotifier.fireTestStarted(RunNotifier.java:84) > at > org.junit.internal.runners.model.EachTestNotifier.fireTestStarted(EachTestNotifier.java:41) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:74) > at > com.itasoftware.##.testrunner.CachedIntegrationTestRunner.runChild(CachedIntegrationTestRunner.java:146) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > org.apache.maven.surefire.junitcore.SynchronousRunner.schedule(SynchronousRunner.java:7) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.ConcurrentModificationException > at > java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at > org.apache.maven.surefire.junitcore.LogicalStream.writeDetails(LogicalStream.java:85) > at > org.apache.maven.surefire.junitcore.TestMethod.replay(TestMethod.java:101) > at org.apache.maven.surefire.junitcore.TestSet.replay(TestSet.java:83) > ... 26 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-707) NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on test class)
[ http://jira.codehaus.org/browse/SUREFIRE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258419#action_258419 ] Kristian Rosenvold commented on SUREFIRE-707: - Plexus utils 2.0.7 will be appearing in maven central in a few hours. Adding this to surefire should solve this issue; maven-surefire-plugin org.codehaus.plexus plexus-utils 2.0.7 Please report back on the effects of this. > NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on > test class) > > > Key: SUREFIRE-707 > URL: http://jira.codehaus.org/browse/SUREFIRE-707 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 > Environment: $ mvn -version > Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_22, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix" >Reporter: Mark Renouf > > Captured using a custom RunListener, tracing to a file: > 2011-02-28-13:30:02.137 TEST_FAILED - Test mechanism: null > java.lang.NullPointerException > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testSkipped(ConcurrentReporterManager.java:107) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testIgnored(JUnit4RunListener.java:68) > at > org.junit.runner.notification.RunNotifier$6.notifyListener(RunNotifier.java:130) > at > org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41) > at > org.junit.runner.notification.RunNotifier.fireTestIgnored(RunNotifier.java:127) > at > org.junit.internal.builders.IgnoredClassRunner.run(IgnoredClassRunner.java:19) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > org.apache.maven.surefire.junitcore.ConfigurableParallelComputer$AsynchronousRunner$1.call(ConfigurableParallelComputer.java:185) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-695) Avoid duplicate code in SurefirePlugin and IntegrationTestMojo
[ http://jira.codehaus.org/browse/SUREFIRE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-695: Fix Version/s: (was: 2.7.3) 2.8 > Avoid duplicate code in SurefirePlugin and IntegrationTestMojo > -- > > Key: SUREFIRE-695 > URL: http://jira.codehaus.org/browse/SUREFIRE-695 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.7 >Reporter: Stefan Birkner >Assignee: Kristian Rosenvold > Fix For: 2.8 > > Attachments: SUREFIRE-verifyParameters.patch > > > The methods verifyParameters() and execute() have much code in common. > Therefore I moved these parts of the code to the AbstractSurefireMojo and > created two abstract methods executeAfterPreconditionsChecked() and > isSkipExecution(). For the sake of not changing the API, I didn't change the > visibility of verifyParameters() from public to private. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-711. --- Resolution: Fixed Fix Version/s: 2.8 Assignee: Kristian Rosenvold Identified a memory leak that affects only mostly big reactor builds. This is a really nice catch. Fixed in r1076794 and an updated 2.8-SNAPSHOT is being deployed to repository.apache.org now. Thanks for a good bug report! > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-577) running only some method of a unit class (with -Dtest=MyClass#myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-577: Fix Version/s: (was: 2.7.3) 2.8 > running only some method of a unit class (with -Dtest=MyClass#myMethod) > --- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.8 > > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-699) Remove TestNG from system classpath of forked process
[
http://jira.codehaus.org/browse/SUREFIRE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-699:
Fix Version/s: (was: 2.7.3)
2.8
> Remove TestNG from system classpath of forked process
> -
>
> Key: SUREFIRE-699
> URL: http://jira.codehaus.org/browse/SUREFIRE-699
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, TestNG support
>Affects Versions: 2.7.2
>Reporter: Reinhard Nägele
>Assignee: Kristian Rosenvold
>Priority: Critical
> Fix For: 2.8
>
>
> TestNG is added to the system classloader of the forked test process. Since
> TestNG has a dependency to Guice 2, projects using Guice 3 run into trouble
> because Guice 2 wins.
> The problem can be fixed by commenting out line 1025 in AbstractSurefireMojo:
> public void addProviderArtifactToBootClasspath( Classpath bootclasspath )
> throws ArtifactResolutionException, ArtifactNotFoundException
> {
> // dependencyResolver.addResolvedArtifactToClasspath( bootclasspath,
> testNgArtifact );
> }
> Related discussions:
> http://maven.40175.n5.nabble.com/Problems-with-Surefire-TestNG-and-Guice-3-td3384082.html
> http://groups.google.com/group/testng-users/browse_thread/thread/db58d13ca498bb92
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-698) 4.7 provider ignores junit-dep
[ http://jira.codehaus.org/browse/SUREFIRE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-698: Fix Version/s: (was: 2.7.3) 2.8 > 4.7 provider ignores junit-dep > -- > > Key: SUREFIRE-698 > URL: http://jira.codehaus.org/browse/SUREFIRE-698 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.6, 2.7, 2.7.1, 2.7.2 >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.8 > > > It was pointed out on IRC that the 4.7 provider does not detect junit-dep > like it should -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-566) Bump to Doxia 1.1.1
[ http://jira.codehaus.org/browse/SUREFIRE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-566: Fix Version/s: (was: 2.7.3) 2.8 > Bump to Doxia 1.1.1 > --- > > Key: SUREFIRE-566 > URL: http://jira.codehaus.org/browse/SUREFIRE-566 > Project: Maven Surefire > Issue Type: Task > Components: Maven Surefire Report Plugin >Affects Versions: 2.4.3 >Reporter: Vincent Siveton >Assignee: Lukas Theussl > Fix For: 2.8 > > Attachments: surefire566VersionUpdates.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-696) Improve the design of the class Classpath
[ http://jira.codehaus.org/browse/SUREFIRE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-696: Fix Version/s: (was: 2.7.3) 2.8 > Improve the design of the class Classpath > - > > Key: SUREFIRE-696 > URL: http://jira.codehaus.org/browse/SUREFIRE-696 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.7.2 >Reporter: Stefan Birkner >Priority: Minor > Fix For: 2.8 > > Attachments: SUREFIRE-696.patch, SUREFIRE-Classpath.patch > > > This patch contains some improvements for the class Classpath: > * Only use a set for storing the elements. > * append(Classpath) has been changed to Classpath.join(Classpath, Classpath), > because the classpath doesn't get appended. Instead a new one is created. > * Renamed setForkProperties to writeToForkProperties. > * Renamed setAsSystemProperty to writeToSystemProperty. > * Moved getClassPathAsString() into writeToSystemProperty and only call > writeToSystemProperty from outside. > * Added readFromForkProperties in order to have serialization and > deseralization being part of the same class. > From my point of view these changes improve the readability of the Surefire > code and are another step on the way to clean code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-689) Non-working links on the m-failsafe-p site
[ http://jira.codehaus.org/browse/SUREFIRE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-689: Fix Version/s: (was: 2.7.3) 2.8 > Non-working links on the m-failsafe-p site > -- > > Key: SUREFIRE-689 > URL: http://jira.codehaus.org/browse/SUREFIRE-689 > Project: Maven Surefire > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.1 > Environment: n/a >Reporter: Anders Hammar >Assignee: Kristian Rosenvold >Priority: Trivial > Fix For: 2.8 > > Attachments: SUREFIRE-689.patch > > > There are several non-working links on the failsafe plugin's site. For > example, on the first page: > * Non of the links to the two goals work > * Under Usage, several of the links don't work > * The links to the examples don't work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-700: Fix Version/s: (was: 2.7.3) 2.8 > Surefire is not isolated from itself > > > Key: SUREFIRE-700 > URL: http://jira.codehaus.org/browse/SUREFIRE-700 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.4.1, 2.4.2, 2.4.3, 2.5, 2.6, 2.7, 2.7.1, 2.7.2 >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.8 > > Attachments: stage2.patch > > > The current classloader structure in surefire does not isolate surefire from > changes to surefire in itself. This means an interface change in *most* > private interfaces and classes can break the build of surefire itself. > This is due to the classloader structure > systemclassloader<-testclassloader<-providerclassloader, where a modified > surefire immediately becomes effective by being loaded in testclassloader. > This issue will be fixed by making the following structure: > systemclassloader<-testframeworkclassloader<-testclassloader > systemclassloader<-testframeworkclassloader<-surefireclassloader > Pardon the ascii graphics but it seems like jira does not allow me to draw > systemclassloader<-testframeworkclassloader as one common root ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-694) NPE when empty additionalClasspathElement
[
http://jira.codehaus.org/browse/SUREFIRE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-694:
Fix Version/s: (was: 2.7.3)
2.8
> NPE when empty additionalClasspathElement
> -
>
> Key: SUREFIRE-694
> URL: http://jira.codehaus.org/browse/SUREFIRE-694
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 3.x support
>Affects Versions: 2.7.2
>Reporter: Michiel Kalkman
>Assignee: Kristian Rosenvold
>Priority: Trivial
> Fix For: 2.8
>
> Attachments: SUREFIRE-694.patch
>
>
> Just add to your pom something like:
>
>
>
> maven-surefire-plugin
> 2.7.2
>
>
>
>
> or
> ${abc}
> where ${abc} does not resolve.
> This results in a npe:
> [INFO] Trace
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:394)
> at java.util.Properties.setProperty(Properties.java:143)
> at
> org.apache.maven.surefire.booter.Classpath.setForkProperties(Classpath.java:139)
> at
> org.apache.maven.surefire.booter.ClasspathConfiguration.setForkProperties(ClasspathConfiguration.java:89)
> at
> org.apache.maven.plugin.surefire.booterclient.BooterSerializer.serialize(BooterSerializer.java:79)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:180)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-690: Fix Version/s: (was: 2.7.3) 2.8 > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > Fix For: 2.8 > > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-704) maven surefire Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice
[ http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258436#action_258436 ] Kristian Rosenvold commented on SUREFIRE-704: - Unfortunately this issue will not be fixed before earliest 2.8.1, because the kind of code change required has not been possible until SUREFIRE-700 has been released. Please note, Chad Wilson, that adding the following to your plugin defintion will probably remove the randomness you are experiencing (and it's a good thing to do this immediately even with 2.7.2 if you're using fork timeout): Plexus utils 2.0.7 will be appearing in maven central in a few hours. Adding this to surefire should solve this issue; maven-surefire-plugin org.codehaus.plexus plexus-utils 2.0.7 This *will* be fixed for 2.8 > maven surefire Error while executing forked tests.; nested exception is > java.lang.IllegalStateException: testSetStarting called twice > - > > Key: SUREFIRE-704 > URL: http://jira.codehaus.org/browse/SUREFIRE-704 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.7.2 > Environment: Windows/Linux/SunOS >Reporter: S Daigle > Attachments: surefire-272.txt, surefire.txt > > > We want to upgrade from our current 2.5 version of the maven-surefire-plugin > to something newer but cannot get past the error below. We've tried versions > 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail. > When setting forkmode to "once" and redirectTestOutputToFile to "true", we > get the following error on multiple tests: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test > (default-test) on project api: Error while executing forked tests.; nested > exception is java.lang.IllegalStateException: testSetStarting called twice -> > [Help 1] > Please see the attachment for full "mvn -e test" output. > If we set the redirectTestOutputToFile to false, it works but we need this > option set to true. > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-646) Overlapping -D's for surefire and failsafe make it hard to control combination
[ http://jira.codehaus.org/browse/SUREFIRE-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-646: Issue Type: New Feature (was: Bug) > Overlapping -D's for surefire and failsafe make it hard to control combination > -- > > Key: SUREFIRE-646 > URL: http://jira.codehaus.org/browse/SUREFIRE-646 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.6 >Reporter: Benson Margulies > > I have a project with both surefire unit tests and failsafe integration > tests. This works until I try to start controlling things from command line. > 1. Both plugins respect -DskipTests. failsafe has skipITs, but surefire does > not seem to have a corresponding property that just skips the unit tests, not > the integration tests. > 2. When I use -Dtest= and specify an integration test, SUREFIRE runs it > before failsafe gets a chance, and of course it fails because the > pre-integration-test phase hasn't set up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258470#action_258470 ] Gin-Ting Chen commented on SUREFIRE-690: I got another one today after setting timeout to 0. I haven't verified yet that it was running with no timeout settings but it was the first one since setting it. So it definitely seems to be related as it happened way more frequently before. I will try it again now with the new plexus-utils but I can't guarantee that I will know the results anytime soon as this is intermittent and I still haven't had time to come up with a test case. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > Fix For: 2.8 > > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-710) ConcurrentModificationException in ConcurrentReporterManager
[ http://jira.codehaus.org/browse/SUREFIRE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-710. --- Resolution: Fixed Fixed in r1077831. The problem is related to redirectTestOutputToFile=true, and there have been a number of issues in the 2.7 range regarding this flag. Please re-test 2.8-SNAPSHOT and do not hesitate to re-open issue with additional details if it happens again. 2.8 will be releasing next week and I'd like to get this sorted out before 2.8. > ConcurrentModificationException in ConcurrentReporterManager > > > Key: SUREFIRE-710 > URL: http://jira.codehaus.org/browse/SUREFIRE-710 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 > Environment: $ mvn -version > Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_22, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix" >Reporter: Mark Renouf > > Captured using custom RunListener, tracing to a file: > 2011-02-28-17:05:30.377 TEST_FAILED - Test mechanism: > java.util.ConcurrentModificationException > 2011-02-28-17:05:30.378 java.lang.RuntimeException: > java.util.ConcurrentModificationException > at org.apache.maven.surefire.junitcore.TestSet.replay(TestSet.java:91) > at > org.apache.maven.surefire.junitcore.TestSet.setAllScheduled(TestSet.java:134) > at > org.apache.maven.surefire.junitcore.ClassesParallelRunListener.checkIfTestSetCanBeReported(ClassesParallelRunListener.java:47) > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testStarting(ConcurrentReporterManager.java:123) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testStarted(JUnit4RunListener.java:79) > at > org.junit.runner.notification.RunNotifier$3.notifyListener(RunNotifier.java:87) > at > org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41) > at > org.junit.runner.notification.RunNotifier.fireTestStarted(RunNotifier.java:84) > at > org.junit.internal.runners.model.EachTestNotifier.fireTestStarted(EachTestNotifier.java:41) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:74) > at > com.itasoftware.##.testrunner.CachedIntegrationTestRunner.runChild(CachedIntegrationTestRunner.java:146) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > org.apache.maven.surefire.junitcore.SynchronousRunner.schedule(SynchronousRunner.java:7) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.ConcurrentModificationException > at > java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at > org.apache.maven.surefire.junitcore.LogicalStream.writeDetails(LogicalStream.java:85) > at > org.apache.maven.surefire.junitcore.TestMethod.replay(TestMethod.java:101) > at org.apache.maven.surefire.junitcore.TestSet.replay(TestSet.java:83) > ... 26 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-707) NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on test class)
[ http://jira.codehaus.org/browse/SUREFIRE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-707. --- Resolution: Fixed Fix Version/s: 2.8 Assignee: Kristian Rosenvold Fixed in r1077831. The problem is related to redirectTestOutputToFile=true, and there have been a number of issues in the 2.7 range regarding this flag. Please re-test 2.8-SNAPSHOT and do not hesitate to re-open issue with additional details if it happens again. 2.8 will be releasing next week and I'd like to get this sorted out before 2.8. > NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on > test class) > > > Key: SUREFIRE-707 > URL: http://jira.codehaus.org/browse/SUREFIRE-707 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 > Environment: $ mvn -version > Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_22, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix" >Reporter: Mark Renouf >Assignee: Kristian Rosenvold > Fix For: 2.8 > > > Captured using a custom RunListener, tracing to a file: > 2011-02-28-13:30:02.137 TEST_FAILED - Test mechanism: null > java.lang.NullPointerException > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testSkipped(ConcurrentReporterManager.java:107) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testIgnored(JUnit4RunListener.java:68) > at > org.junit.runner.notification.RunNotifier$6.notifyListener(RunNotifier.java:130) > at > org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41) > at > org.junit.runner.notification.RunNotifier.fireTestIgnored(RunNotifier.java:127) > at > org.junit.internal.builders.IgnoredClassRunner.run(IgnoredClassRunner.java:19) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at > org.apache.maven.surefire.junitcore.ConfigurableParallelComputer$AsynchronousRunner$1.call(ConfigurableParallelComputer.java:185) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258491#action_258491 ] Kristian Rosenvold commented on SUREFIRE-690: - OK, this indicates that there are probably several distinct issues causing this problem. You can either add plexus to your surefire-declaration (2.7.2) or just switch to 2.8-SNAPSHOT. Could you give me some indication of the frequency of this issue in its current state ? The redirectTestOuputToFile logice is due for a revision in 2.8.1 or so, and it's basically the source of all these troubles. Is the remaining frequency is more in the "annoyance" category? > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > Fix For: 2.8 > > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
