Sure, go ahead! -Vincent
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: mercredi 6 octobre 2004 22:45 > To: [EMAIL PROTECTED] > Subject: Maven, Cactus, and changing classpath for container startup (part > 2) > > Vincent, > I would like to take advantage of the pathelement feature of > containerclasspath with maven: > > <containerclasspath> > ... > <pathelement path="/some/path/here" /> > </containerclasspath> > > So that I can add a directory to the container classpath (I have > *.properties files that the code depends on). > > This one seems straightforward. If a new property is added (something > like > cactus.container.classpath.path). If the property is detected add an > extra > pathelement before starting up the container. > > If you approve, I don't mind working on the enhancement. > > thanks, > Marc > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 22, 2004 11:19 AM > To: [EMAIL PROTECTED] > Subject: RE: Maven, Cactus, and changing classpath for container startup > > > I will start implementing it today. Thanks for the suggestion. > > Marc > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 22, 2004 12:18 AM > To: 'Cactus Users List' > Subject: RE: Maven, Cactus, and changing classpath for container startup > > > Hi Marc, > > There is a way in the Ant task by using the <containerclasspath> nested > element. > > However, this containerclasspath is not exposed in the Maven plugin for > Cactus. Here's how I would do it if you're interested to implement it: by > adding a special property tag in project.xml for the dependencies (e.g. > cactus.container.classpath) and then iterating over those in jelly to add > to > the <containerclasspath> element. > > Thanks > -Vincent > > PS: I'll have a look today at your patch you've submitted yesterday. > Thanks > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Sent: mercredi 22 septembre 2004 02:56 > > To: [EMAIL PROTECTED] > > Subject: Maven, Cactus, and changing classpath for container startup > > > > Is there a way to configure the classpath setting for the container on > > startup when using the Maven/Cactus plugin? > > > > I want to add C:\domains\lib\wlstartup-8.78.0.jar to my classpath along > > with > > the weblogic.jar. > > > > In my situation I have a config.xml file (weblogic7.x) with an entry for > a > > startup class: > > <StartupClass > > > > > Arguments="filename="global.properties",filelocation="C:\\d > > om > > ains\\conf\\"" > > ClassName="wlstartup.GlobalStartUp" > > LoadBeforeAppDeployments="true" Name="GlobalStartUp" > > Targets="testserver"/> > > > > This startup class is used in all my applications so my test cases fail > if > > certain properties aren't there. > > > > Any help is appreciated. > > Marc > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
