Bummer... highly sucky that we must clean to make a build. Stuff
like this negates some of the intelligence the build uses to reduce
the amount of work (and time to execute).
In general I recommend that a normal build never need to clean, move
or delete files, so that steps that have completed previously do not
need to be redone (where applicable).
Anyways, not a major issue right now, but going forward we will want
to clean this up.
* * *
Is it the local module's target than needs to be cleaned? If so, we
can add a step that runs before car to invoke the clean plugin's
clean goal. This is only a short-term fix though, I do not recommend
that we start adding this pre-cleaning anywhere else.
--jason
On Jul 1, 2006, at 12:47 PM, David Jencks wrote:
The packaging plugin needs to be made to do a clean first, the m1
plugin did this with jelly.
I always run mvn -o clean install inside configs, which is
annoying, but I haven't had time to investigate how to do "clean"
from within an m2 plugin. Maybe you or someone else knows how?
thanks
david jencks
On Jul 1, 2006, at 12:17 PM, Jason Dillon wrote:
This happens during the m2 build... and actually the build ends up
cycling between 2 errors, this one and another that is an internal
plugin error regarding some JCL classes...
:-(
At least it appears to switch back and forth between these two
errors and is not completly random... but still its _whack_ that
the same build fails in different ways on consecutive runs.
I was just running this over and over:
mvn -o -Dmaven.test.skip=true
(with changes applied from GERONIMO-2161)
--jason
On Jul 1, 2006, at 12:08 PM, Jacek Laskowski wrote:
On 7/1/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Is there any reason why a rebuild (with no clean) would cause
errors
like this:
<snip>
[INFO]
-------------------------------------------------------------------
-----
[ERROR] BUILD ERROR
[INFO]
-------------------------------------------------------------------
-----
[INFO] java.lang.reflect.InvocationTargetException
Configuration already exists: org.apache.geronimo.configs/rmi-
naming/
1.2-SNAPSHOT/car
</snip>
Just a guess, isn't Geronimo already populated with the config and
thus the error? I believe the script uses deploy nor redeploy. What
command did you use? It's M1 build, isn't it?
--jason
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
