I had used maven's natural lexical sorting order and 'provided' scope
to make sure that the configs were built in the correct order. The
provided scope was ignored by the car plugin. What mechanism is used
now to enforce the build order?
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
On Dec 1, 2006, at 6:03 AM, anita kulshreshtha wrote:
I had used maven's natural lexical sorting order and 'provided'
scope
to make sure that the configs were built in the correct order. The
provided scope was ignored by the car plugin. What mechanism is used
now to enforce the build
The problem here is that the dependencies on the deployers which the
car plugins use are not part of the reactor's list of dependencies
implicitly. So each car module needs to explicitly depend on the
config of its deployer or mvn will build things out of order.
This will bite you more if
I keep getting this on a clean build:
snip
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
