Re: surefire-report-plugin running tests of all dependent modules again?
I would like to second this sentiment. Is there a plugin that can add the current plugin version information to the pom? I also definately think this information should be added to poms processed with the release plugin (if it isn't already). Thanks On Jan 29, 2008 5:49 PM, Joerg Hohwiller [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | Hi Jörg, Hi Stefan, | | this is also what I see here (see my post about M2 multi-project site | build is broken). | All tests are run for each project in the reactor. I think we could file | an issue for each of the affected plugins, but this seems more like a | maven generic issue. Something was fixed with devastating effects for | a lot of plugins. What maven version are you using? I am using maven 2.0.8 Everything works fine if I explicitly set the version of the surefire-report-plugin to 2.3 and goes wrong if I use 2.4 I did not have the same problem with other plugins. Could you track this down? Though I know that the latest site-plugin is buggy as well as the latest javadoc-plugin. But this are other problems. If you want freedom with maven you need to define the versions of all plugins explicitly in your toplevel pom. That is what I learned in a bloody bad lessen with maven. The plugin developers often do not know the impact of releasing buggy plugins. There are thousands of maven users that suddenly have a broken build and no idea what is wrong. I am using maven from the early days now and switched to maven2 over 2,5 years ago. With maven2 I want to build my code and the project website. The site of a multi-project build was a problem for years and even though patches are attached to jira for fixing related plugins such as cobertura it is still not fixed. Sometimes you need to be patient. However maven2 is excellent already and I have big hopes for maven 2.1 all that is going on with mojo, etc. After a lot of pain with maven1 I am happy to see a product with a design and a concept. Thanks to all the great workers of the maven team! | | Stefan Regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHn62GmPuec2Dcv/8RAtzeAJ92rvs3JmZmkseghuWYW1/N+GsDRQCfXSxI 8P1+VCIkc4HEJIKxZjXnZZs= =SZo2 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: surefire-report-plugin running tests of all dependent modules again?
Hi Jörg,
this is also what I see here (see my post about M2 multi-project site
build is broken).
All tests are run for each project in the reactor. I think we could file
an issue for each of the affected plugins, but this seems more like a
maven generic issue. Something was fixed with devastating effects for
a lot of plugins. What maven version are you using?
Stefan
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
| Try
|
| export MAVEN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
oh, stupid me!
The build runs now, but still it is true what I described:
It seems to cycle. It is not an infinity loop but the same modules
are build and tested again and again.
Might be a bug introduced in maven-surefire-report-plugin 2.4.
I build with 2.4.
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 27 minutes 57 seconds
[INFO] Finished at: Mon Jan 28 23:16:26 GMT+01:00 2008
[INFO] Final Memory: 92M/164M
[INFO]
Then I ran a clean build again with maven-surefire-report-plugin 2.3
and got:
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 9 minutes 38 seconds
[INFO] Finished at: Mon Jan 28 23:29:44 GMT+01:00 2008
[INFO] Final Memory: 46M/86M
[INFO]
The log (maven-output) is multiple times larger with 2.4.
Any ideas?
Shall I file a jira issue?
|
| instead.
|
| As far as I can see, MVN_OPTS is not used by Maven.
Thanks for this hint.
Take care
~ Jörg
|
|
| On 27/01/2008, Joerg Hohwiller [EMAIL PROTECTED] wrote:
| Hi there,
|
| the build of my projects site does not work anymore.
|
| I do this:
|
| export MVN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
| mvn install -Dmaven.test.skip=true
| mvn -npu -fae -Pcodehaus site:stage -DstagingDirectory=${STAGE_DIR}
|
| The problem occured since I hat to purge my local repository.
| I currently guess that it has to do something with a bug in a new
| released plugin (maybe related to surefire - see below).
|
| Can anybody help me to track this down?
|
| After an extra-ordinary long build I got this error:
|
| [INFO] Generate Source Xref report.
| [INFO]
| [ERROR] FATAL ERROR
| [INFO]
| [INFO] Java heap space
| [INFO]
| [INFO] Trace
| java.lang.OutOfMemoryError: Java heap space
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(VelocityCharStream.java:260)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(VelocityCharStream.java:296)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(VelocityCharStream.java:302)
| ~at
org.apache.velocity.runtime.parser.Parser.init(Parser.java:61)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.createNewParser(RuntimeInstance.java:694)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.initializeParserPool(RuntimeInstance.java:681)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:229)
| ~at
org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:80)
| ~at
org.apache.maven.jxr.DirectoryIndexer.process(DirectoryIndexer.java:220)
| ~at org.apache.maven.jxr.JXR.xref(JXR.java:281)
| ~at
|
org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrReport.java:261)
|
|
| The build also seems to cycle because it does the same things again
and again.
| During that it logs sections like this:
| Tests run: 8, Failures: 0, Errors: 0, Skipped: 1
|
| [INFO] Preparing surefire-report:report-only
| [INFO]
| [INFO] Building mmm
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util-core
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util-reflect
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
Re: surefire-report-plugin running tests of all dependent modules again?
Hi Stefan,
For me, it happens on 2.0.7 and 2.0.8 with java 1.5.0_14
Erez.
On Jan 29, 2008 10:07 AM, VUB Stefan Seidel [EMAIL PROTECTED] wrote:
Hi Jörg,
this is also what I see here (see my post about M2 multi-project site
build is broken).
All tests are run for each project in the reactor. I think we could file
an issue for each of the affected plugins, but this seems more like a
maven generic issue. Something was fixed with devastating effects for
a lot of plugins. What maven version are you using?
Stefan
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
| Try
|
| export MAVEN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
oh, stupid me!
The build runs now, but still it is true what I described:
It seems to cycle. It is not an infinity loop but the same modules
are build and tested again and again.
Might be a bug introduced in maven-surefire-report-plugin 2.4.
I build with 2.4.
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 27 minutes 57 seconds
[INFO] Finished at: Mon Jan 28 23:16:26 GMT+01:00 2008
[INFO] Final Memory: 92M/164M
[INFO]
Then I ran a clean build again with maven-surefire-report-plugin 2.3
and got:
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 9 minutes 38 seconds
[INFO] Finished at: Mon Jan 28 23:29:44 GMT+01:00 2008
[INFO] Final Memory: 46M/86M
[INFO]
The log (maven-output) is multiple times larger with 2.4.
Any ideas?
Shall I file a jira issue?
|
| instead.
|
| As far as I can see, MVN_OPTS is not used by Maven.
Thanks for this hint.
Take care
~ Jörg
|
|
| On 27/01/2008, Joerg Hohwiller [EMAIL PROTECTED] wrote:
| Hi there,
|
| the build of my projects site does not work anymore.
|
| I do this:
|
| export MVN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
| mvn install -Dmaven.test.skip=true
| mvn -npu -fae -Pcodehaus site:stage -DstagingDirectory=${STAGE_DIR}
|
| The problem occured since I hat to purge my local repository.
| I currently guess that it has to do something with a bug in a new
| released plugin (maybe related to surefire - see below).
|
| Can anybody help me to track this down?
|
| After an extra-ordinary long build I got this error:
|
| [INFO] Generate Source Xref report.
| [INFO]
| [ERROR] FATAL ERROR
| [INFO]
| [INFO] Java heap space
| [INFO]
| [INFO] Trace
| java.lang.OutOfMemoryError: Java heap space
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:260)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:296)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:302)
| ~at
org.apache.velocity.runtime.parser.Parser.init(Parser.java:61)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.createNewParser(
RuntimeInstance.java:694)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.initializeParserPool(
RuntimeInstance.java:681)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java
:229)
| ~at
org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:80)
| ~at
org.apache.maven.jxr.DirectoryIndexer.process(DirectoryIndexer.java:220)
| ~at org.apache.maven.jxr.JXR.xref(JXR.java:281)
| ~at
|
org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(
AbstractJxrReport.java:261)
|
|
| The build also seems to cycle because it does the same things again
and again.
| During that it logs sections like this:
| Tests run: 8, Failures: 0, Errors: 0, Skipped: 1
|
| [INFO] Preparing surefire-report:report-only
| [INFO]
| [INFO] Building mmm
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util-core
| [INFO]
Re: surefire-report-plugin running tests of all dependent modules again?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | Hi Jörg, Hi Stefan, | | this is also what I see here (see my post about M2 multi-project site | build is broken). | All tests are run for each project in the reactor. I think we could file | an issue for each of the affected plugins, but this seems more like a | maven generic issue. Something was fixed with devastating effects for | a lot of plugins. What maven version are you using? I am using maven 2.0.8 Everything works fine if I explicitly set the version of the surefire-report-plugin to 2.3 and goes wrong if I use 2.4 I did not have the same problem with other plugins. Could you track this down? Though I know that the latest site-plugin is buggy as well as the latest javadoc-plugin. But this are other problems. If you want freedom with maven you need to define the versions of all plugins explicitly in your toplevel pom. That is what I learned in a bloody bad lessen with maven. The plugin developers often do not know the impact of releasing buggy plugins. There are thousands of maven users that suddenly have a broken build and no idea what is wrong. I am using maven from the early days now and switched to maven2 over 2,5 years ago. With maven2 I want to build my code and the project website. The site of a multi-project build was a problem for years and even though patches are attached to jira for fixing related plugins such as cobertura it is still not fixed. Sometimes you need to be patient. However maven2 is excellent already and I have big hopes for maven 2.1 all that is going on with mojo, etc. After a lot of pain with maven1 I am happy to see a product with a design and a concept. Thanks to all the great workers of the maven team! | | Stefan Regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHn62GmPuec2Dcv/8RAtzeAJ92rvs3JmZmkseghuWYW1/N+GsDRQCfXSxI 8P1+VCIkc4HEJIKxZjXnZZs= =SZo2 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: surefire-report-plugin running tests of all dependent modules again?
We have same issue here.
I can send my test project if anyone would like to check.
It is a multi mudule project, using surefire 2.4 and maven 2.0.8, Java
1.5.0_14 and the issue is when running mvn site:siet
Thanks,
Erez.
On Jan 29, 2008 12:30 AM, Joerg Hohwiller [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
| Try
|
| export MAVEN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
oh, stupid me!
The build runs now, but still it is true what I described:
It seems to cycle. It is not an infinity loop but the same modules
are build and tested again and again.
Might be a bug introduced in maven-surefire-report-plugin 2.4.
I build with 2.4.
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 27 minutes 57 seconds
[INFO] Finished at: Mon Jan 28 23:16:26 GMT+01:00 2008
[INFO] Final Memory: 92M/164M
[INFO]
Then I ran a clean build again with maven-surefire-report-plugin 2.3 and
got:
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 9 minutes 38 seconds
[INFO] Finished at: Mon Jan 28 23:29:44 GMT+01:00 2008
[INFO] Final Memory: 46M/86M
[INFO]
The log (maven-output) is multiple times larger with 2.4.
Any ideas?
Shall I file a jira issue?
|
| instead.
|
| As far as I can see, MVN_OPTS is not used by Maven.
Thanks for this hint.
Take care
~ Jörg
|
|
| On 27/01/2008, Joerg Hohwiller [EMAIL PROTECTED] wrote:
| Hi there,
|
| the build of my projects site does not work anymore.
|
| I do this:
|
| export MVN_OPTS=-Xmx1024M -XX:MaxPermSize=512m
| mvn install -Dmaven.test.skip=true
| mvn -npu -fae -Pcodehaus site:stage -DstagingDirectory=${STAGE_DIR}
|
| The problem occured since I hat to purge my local repository.
| I currently guess that it has to do something with a bug in a new
| released plugin (maybe related to surefire - see below).
|
| Can anybody help me to track this down?
|
| After an extra-ordinary long build I got this error:
|
| [INFO] Generate Source Xref report.
| [INFO]
| [ERROR] FATAL ERROR
| [INFO]
| [INFO] Java heap space
| [INFO]
| [INFO] Trace
| java.lang.OutOfMemoryError: Java heap space
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:260)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:296)
| ~at
|
org.apache.velocity.runtime.parser.VelocityCharStream.init(
VelocityCharStream.java:302)
| ~at org.apache.velocity.runtime.parser.Parser.init(Parser.java
:61)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.createNewParser(
RuntimeInstance.java:694)
| ~at
|
org.apache.velocity.runtime.RuntimeInstance.initializeParserPool(
RuntimeInstance.java:681)
| ~at
| org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java
:229)
| ~at org.apache.velocity.app.VelocityEngine.init(
VelocityEngine.java:80)
| ~at
org.apache.maven.jxr.DirectoryIndexer.process(DirectoryIndexer.java:220)
| ~at org.apache.maven.jxr.JXR.xref(JXR.java:281)
| ~at
|
org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(
AbstractJxrReport.java:261)
|
|
| The build also seems to cycle because it does the same things again and
again.
| During that it logs sections like this:
| Tests run: 8, Failures: 0, Errors: 0, Skipped: 1
|
| [INFO] Preparing surefire-report:report-only
| [INFO]
| [INFO] Building mmm
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util-core
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO] Building util-reflect
| [INFO]
| [INFO] No goals needed for project - skipping
| [INFO]
| [INFO]
