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
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
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
-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
-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
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:
