We need to delete target/repository to preserve the work done by
the earlier operation (car:dependencies). The M2 plugin will also have
code to delete this directory. Since we run both M1 and M2 builds and
the generated plans are different for each, it is necessary to delete
the target
Is there any reason why a rebuild (with no clean) would cause errors
like this:
snip
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO]
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]
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
This helped us ensure that we always have a clean environment for
the configuration being packaged. As soon as we have our first server
that starts, this restriction will be removed.
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
Is there any reason why a rebuild (with no clean)
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
FYI, re-adding the JCL dependency fixes one of the problems...
--jason
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
FYI, this in the configs/pom.xml should do the trick:
build
plugins
!--
| NOTE: Currently to build CAR files, we need to
ensure that the module has been cleaned first
| otherwise the second time around the build
will fail.
On Jul 1, 2006, at 2:14 PM, Jason Dillon wrote:
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,
