Hi Brian, Yep, this is a current limitation of the <jboss3x> container in Cactus. It currently does not support "external" configurations. It'll look for them under [jbosshome]/server/.
This is something that we need to fix of course as it's supported for all other containers. Just not had the time yet. Do you think you could create a JIRA issue for this and assign it for version 1.7? Thanks -Vincent > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: 05 May 2004 17:40 > To: [EMAIL PROTECTED] > Subject: Specification JBoss server configuration directory with maven > plugin > > After digging through the mailing list archive, I noticed that at one time > the maven plugin supported a property: > > cactus.jboss3x.config.dir > > Which specified the location of the Jboss server configuration directory. > As far as I can tell, this property no longer exists. Is there an > alternative way to specify the location of this directory? I am using the > maven jboss plugin to create a custom, project-specific, jboss > configuration > directory structure, and would like to be able to point the cactus plugin > at > this directory. IE, I am looking for the equivalent of setting the > following 2 properties: > > cactus.jboss3x.config.dir='my custom configuration directory' > cactus.jboss3x.config.name='my custom server configuration' > > Thanks. > > - Brian > > --------------------------------------------------------------------- > 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]
