----- Original Message ----- From: "Farr, Aaron" <[EMAIL PROTECTED]>
Umm... I just did a clean check out of the Avalon module (not just fortress), then ran "maven jar:jar" in the avalon/fortress/container directory and not only did everything build (downloaded the needed dependencies), but all the unit tests passed too.
I'm trying to do the same thing but I can't. Seems a cyclic dependency issue.
yep. It's been a TODO for ages. ie:
http://cvs.apache.org/viewcvs.cgi/avalon/fortress/container/project.xml?r1=1.7&r2=1.8&diff_format=h
the tools are used for running the container tests IIRC. A workaround is to comment out the dependency on tools in the container project.xml file (as above), build it and install it into your local repo. Disable the tests. IOW,
cd avalon/fortress/container maven jar:install -Dmaven.test.skip=yes
then, build the tools
cd ../tools maven jar:install
then, build and install with the tests
cd ../container maven jar:install
The appropriate fix is to disable the use of the tools package in the container package. Patches most welcome :D
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
