This is a symptom of a different problem, that you can't build a plugin
and use it in the same build (at least not reliably, as far as I can
tell) magicGball now uses the deployment plugin which has deploy-jsr88
as a dependency. If the plugin isn't built you will get a related
error when you get to assembly.
It might help to include a dependency on the deploy plugin in
project.xml. However, I have faint memories that this might cause
other problems. In general I've found maven 1 to have problems
building a plugin and using it in the same multiproject build. I don't
know if this is fixed in maven 1.1, I believe it is fixed in maven 2.
Wish I had better news,
david jencks
On Oct 1, 2005, at 8:09 AM, Aaron Mulder wrote:
When I do a rebuild-all on HEAD, I get (eventually):
+----------------------------------------
| Executing default The Magic G Ball
| Memory: 67M/83M
+----------------------------------------
You are working offline so the build will continue, but
geronimo-common-1.0-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
geronimo-kernel-1.0-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
geronimo-deployment-1.0-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
geronimo-system-1.0-SNAPSHOT.jar may be out of date!
BUILD FAILED
File......
/Users/ammulder/.maven/cache/maven-multiproject-plugin-1.3.1/
plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
The build cannot continue because of the following unsatisfied
dependency:
geronimo-deploy-jsr88-1.0-SNAPSHOT.jar
Total time: 4 minutes 44 seconds
Finished at: Sat Oct 01 10:53:15 EDT 2005
I don't understand why it wants geronimo-deploy-jsr88 even though
that's not listed as a dependency in project.xml for the magic G ball.
In any case, if that's a prerequisite, shouldn't something force the
deploy-jsr88 module to be built before the magic G ball module?
Thanks,
Aaron
