Hi Darren, The <cactus.bundle> directive tells the plugin to bundle the jar in the cactified WAR. It doesn't include any jar in the EAR.
The <ear.bundle> directive was not supported by the Cactus plugin. I've just committed a fix for this in CVS. The ear behavior of the Cactus plugin when running the cactus:test-ear goal is now in sync with the one from the EAR Maven plugin. You'll need to build the plugin from CVS though to use it (quite easy to do actually - simply checkout jakarta-cactus, cd to integration/maven and type "maven plugin:install"). I'll also try to create a nightly build release for the plugin in a few days. Thanks -Vincent > -----Original Message----- > From: Darren Hartford [mailto:[EMAIL PROTECTED] > Sent: 16 February 2004 17:13 > To: [EMAIL PROTECTED] > Subject: cactus:test-ear and <cactus.bundle> tag for Maven Integration? > > Hey all, > In my project.xml file, I have the following properties for some dependent > files: > <properties> > <cactus.bundle>true</cactus.bundle> > <ear.bundle>true</ear.bundle> > </properties> > > When running either: > cactus:cactifyear > cactus:test-ear > > When I explode the EAR, those identified files are not included in the > generated *-CACTUS.ear file. Is this the correct approach to include > dependent files? > > -D > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
