You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by VUB Stefan Seidel <ss...@vub.de> on 2008/01/28 14:38:28 UTC
M2 multi-project site build is broken
Hi,
I don't know if anyone else noticed this, but the mvn site keeps on
getting worse. It first started out with the following phenomenon:
during site build, for each project _all_ the projects were iterated,
usually saying
[INFO] No goals needed for project - skipping
Then, we started using xmlbeans and it started doing xmlbeans:xmlbeans
for each project. And now, it executes _all_ the tests of _all_ project
for _each_ project. Well, you can imagine that this is pretty much
undoable for a project like ours with 150+ modules.
Here some sample outputs from the attached project (1 parent, 2 modules,
1 test per module)
> mvn clean site | grep Running | wc -l
6
---> this means the two tests are executed 3 times each!!
> mvn clean site | grep xmlbeans | wc -l
29
---> this means, xmlbeans is being executed 26 times, 9 times per project!!!
Hello? Is anyone _using_ maven 2 & site generation? This situation is
that it is becoming totally unusable. The problem is, I don't even know
where to report the bug, because it seems to be a combination of bugs.
regards,
Stefan Seidel
P.S.: I have removed the attached project, to see whether this is
causing the apache mail server to reject my mail. You can find it at
http://stefanseidel.info/mvnexec.zip
--
best regards,
Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel. +49 (341) 9 60 50 07
fax. +49 (341) 9 60 50 92
mail. sseidel@vub.de
web. www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: M2 multi-project site build is broken
Posted by Mick Knutson <mi...@gmail.com>.
We use XML beans but we use plugin management in the main pom.xml, the:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>xmlbeans-maven-plugin</artifactId>
</plugin>
for the few modules that actually need the create our xml bean.
Are you doing that?
Also, we group our xmlbean modules together and do not run them everytime we
build unless there is a change to the code.
Takes way too long otherwise.
On Jan 29, 2008 1:08 PM, Dennis Lundberg <de...@apache.org> wrote:
> It might be so, but the title of your mail "M2 multi-project site build
> is broken" is not going to attract people who knows about running tests...
>
> VUB Stefan Seidel wrote:
> > Ok, but what about the Surefire tests being run way too often? Is this
> > not a more general error?
> >
> > Stefan
> >
> > Dennis Lundberg wrote:
> >> This sounds like something to report in JIRA for the xmlbeans plugin.
> >>
> >> http://jira.codehaus.org/browse/MXMLBEANS
> >>
> >> VUB Stefan Seidel wrote:
> >>> Hi,
> >>>
> >>> I don't know if anyone else noticed this, but the mvn site keeps on
> >>> getting worse. It first started out with the following phenomenon:
> >>> during site build, for each project _all_ the projects were iterated,
> >>> usually saying
> >>> [INFO] No goals needed for project - skipping
> >>> Then, we started using xmlbeans and it started doing xmlbeans:xmlbeans
> >>> for each project. And now, it executes _all_ the tests of _all_
> project
> >>> for _each_ project. Well, you can imagine that this is pretty much
> >>> undoable for a project like ours with 150+ modules.
> >>>
> >>> Here some sample outputs from the attached project (1 parent, 2
> modules,
> >>> 1 test per module)
> >>> > mvn clean site | grep Running | wc -l
> >>> 6
> >>> ---> this means the two tests are executed 3 times each!!
> >>>
> >>> > mvn clean site | grep xmlbeans | wc -l
> >>> 29
> >>> ---> this means, xmlbeans is being executed 26 times, 9 times per
> >>> project!!!
> >>>
> >>> Hello? Is anyone _using_ maven 2 & site generation? This situation is
> >>> that it is becoming totally unusable. The problem is, I don't even
> know
> >>> where to report the bug, because it seems to be a combination of bugs.
> >>>
> >>>
> >>> regards,
> >>>
> >>> Stefan Seidel
> >>>
> >>> P.S.: I have removed the attached project, to see whether this is
> >>> causing the apache mail server to reject my mail. You can find it at
> >>> http://stefanseidel.info/mvnexec.zip
> >>>
> >>
> >>
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---
Re: M2 multi-project site build is broken
Posted by Dennis Lundberg <de...@apache.org>.
It might be so, but the title of your mail "M2 multi-project site build
is broken" is not going to attract people who knows about running tests...
VUB Stefan Seidel wrote:
> Ok, but what about the Surefire tests being run way too often? Is this
> not a more general error?
>
> Stefan
>
> Dennis Lundberg wrote:
>> This sounds like something to report in JIRA for the xmlbeans plugin.
>>
>> http://jira.codehaus.org/browse/MXMLBEANS
>>
>> VUB Stefan Seidel wrote:
>>> Hi,
>>>
>>> I don't know if anyone else noticed this, but the mvn site keeps on
>>> getting worse. It first started out with the following phenomenon:
>>> during site build, for each project _all_ the projects were iterated,
>>> usually saying
>>> [INFO] No goals needed for project - skipping
>>> Then, we started using xmlbeans and it started doing xmlbeans:xmlbeans
>>> for each project. And now, it executes _all_ the tests of _all_ project
>>> for _each_ project. Well, you can imagine that this is pretty much
>>> undoable for a project like ours with 150+ modules.
>>>
>>> Here some sample outputs from the attached project (1 parent, 2 modules,
>>> 1 test per module)
>>> > mvn clean site | grep Running | wc -l
>>> 6
>>> ---> this means the two tests are executed 3 times each!!
>>>
>>> > mvn clean site | grep xmlbeans | wc -l
>>> 29
>>> ---> this means, xmlbeans is being executed 26 times, 9 times per
>>> project!!!
>>>
>>> Hello? Is anyone _using_ maven 2 & site generation? This situation is
>>> that it is becoming totally unusable. The problem is, I don't even know
>>> where to report the bug, because it seems to be a combination of bugs.
>>>
>>>
>>> regards,
>>>
>>> Stefan Seidel
>>>
>>> P.S.: I have removed the attached project, to see whether this is
>>> causing the apache mail server to reject my mail. You can find it at
>>> http://stefanseidel.info/mvnexec.zip
>>>
>>
>>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: M2 multi-project site build is broken
Posted by VUB Stefan Seidel <ss...@vub.de>.
Ok, but what about the Surefire tests being run way too often? Is this
not a more general error?
Stefan
Dennis Lundberg wrote:
> This sounds like something to report in JIRA for the xmlbeans plugin.
>
> http://jira.codehaus.org/browse/MXMLBEANS
>
> VUB Stefan Seidel wrote:
>> Hi,
>>
>> I don't know if anyone else noticed this, but the mvn site keeps on
>> getting worse. It first started out with the following phenomenon:
>> during site build, for each project _all_ the projects were iterated,
>> usually saying
>> [INFO] No goals needed for project - skipping
>> Then, we started using xmlbeans and it started doing xmlbeans:xmlbeans
>> for each project. And now, it executes _all_ the tests of _all_ project
>> for _each_ project. Well, you can imagine that this is pretty much
>> undoable for a project like ours with 150+ modules.
>>
>> Here some sample outputs from the attached project (1 parent, 2 modules,
>> 1 test per module)
>> > mvn clean site | grep Running | wc -l
>> 6
>> ---> this means the two tests are executed 3 times each!!
>>
>> > mvn clean site | grep xmlbeans | wc -l
>> 29
>> ---> this means, xmlbeans is being executed 26 times, 9 times per
>> project!!!
>>
>> Hello? Is anyone _using_ maven 2 & site generation? This situation is
>> that it is becoming totally unusable. The problem is, I don't even know
>> where to report the bug, because it seems to be a combination of bugs.
>>
>>
>> regards,
>>
>> Stefan Seidel
>>
>> P.S.: I have removed the attached project, to see whether this is
>> causing the apache mail server to reject my mail. You can find it at
>> http://stefanseidel.info/mvnexec.zip
>>
>
>
--
best regards, Stefan Seidel software developer ________________________
VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel. +49
(341) 9 60 50 07 fax. +49 (341) 9 60 50 92 mail. sseidel@vub.de web.
www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss
Neudorf, Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: M2 multi-project site build is broken
Posted by Dennis Lundberg <de...@apache.org>.
This sounds like something to report in JIRA for the xmlbeans plugin.
http://jira.codehaus.org/browse/MXMLBEANS
VUB Stefan Seidel wrote:
> Hi,
>
> I don't know if anyone else noticed this, but the mvn site keeps on
> getting worse. It first started out with the following phenomenon:
> during site build, for each project _all_ the projects were iterated,
> usually saying
> [INFO] No goals needed for project - skipping
> Then, we started using xmlbeans and it started doing xmlbeans:xmlbeans
> for each project. And now, it executes _all_ the tests of _all_ project
> for _each_ project. Well, you can imagine that this is pretty much
> undoable for a project like ours with 150+ modules.
>
> Here some sample outputs from the attached project (1 parent, 2 modules,
> 1 test per module)
> > mvn clean site | grep Running | wc -l
> 6
> ---> this means the two tests are executed 3 times each!!
>
> > mvn clean site | grep xmlbeans | wc -l
> 29
> ---> this means, xmlbeans is being executed 26 times, 9 times per
> project!!!
>
> Hello? Is anyone _using_ maven 2 & site generation? This situation is
> that it is becoming totally unusable. The problem is, I don't even know
> where to report the bug, because it seems to be a combination of bugs.
>
>
> regards,
>
> Stefan Seidel
>
> P.S.: I have removed the attached project, to see whether this is
> causing the apache mail server to reject my mail. You can find it at
> http://stefanseidel.info/mvnexec.zip
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org