Then try a mvn -X build, capture the output with a pipe or tee and start
searching which plugin is executed before the antruns.
Hth,
Nick S.
Erez Nahir wrote:
Thanks Nick,
Nope we do not use surefire reporst, but, maybe another plugin is doing
similar thing.
One of my guesses was that it has to do with plugins the forks the VM, but,
that's also just a guess at this time.
Erez.
On Dec 5, 2007 10:02 PM, Nick Stolwijk <[EMAIL PROTECTED]> wrote:
If I may have a guess, you're using the surefire reports? And all the
antruns are in or before the test phase?
The surefire-report:report goal runs also the mvn test lifecycle. If
this is the case, you can use the surefire-report:report-only goal. Only
make sure that the surefire xml files are already in place, because
those aren't generated in this case.
Hth,
Nick Stolwijk
Erez Nahir wrote:
Thanks Mick and Wendy for your prompt reply,
Mick, unfortunately I can not use this (good) idea, my antrun is running
in
many modules processing different tasks.
I'll try
On Dec 5, 2007 9:20 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
I had this issue, and filtered out the module that used the ant-run
like:
<profiles>
<profile>
<id>documentation</id>
<modules>
<module>business-services</module>
<module>common-c2</module>
</modules>
</profile>
<profile>
<id>no-documentation</id>
<activation>
<property>
<name>build.type</name>
<value>!documentation</value>
</property>
</activation>
<modules>
<module>bpel</module>
<module>business-services</module>
<module>common-c2</module>
</modules>
</profile>
</profiles>
and I just run mvn -P documentation site:site
On Dec 5, 2007 11:17 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On Dec 5, 2007 12:01 PM, Erez Nahir <[EMAIL PROTECTED]> wrote:
I have being trying to ask this question in the past, searched for
forum
and
read documentation, but, no answer yet. I'll try again hopefully I
will
get
an answer (or maybe just hints) what is going on.
So, we have a multi module project with some antrun configuration
running in
some modules during the build.
None of the ant tasks is configure to run in the site lifecycle, all
are
during standard lifecycle.
Without seeing the poms it's really hard to tell. The best thing you
can do is construct the simplest possible example that demonstrates
the problem. Often you'll figure it out yourself while doing that,
but if not, you can zip it up and post a link for someone to look at,
or attach it to a JIRA issue if it seems like there's bug.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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
---
---------------------------------------------------------------------
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]
