Nevermind. The whole thing is just more work than it's worth. Especially since an embedded Jetty 6.x will not place nicely with Selenium.
Thanks anyway, Kevin > -----Original Message----- > From: Kevin Menard [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 13, 2006 10:05 PM > To: Tapestry users > Subject: [SOT] Tapestry, Maven, & Cargo > > Hi all, > > I've been testing for a while using Cargo to start up a new > JVM for Tomcat 5.x. Due to speed issues and debugging > hassle, I'm looking to have Cargo start up an embedded > container instead (here, Jetty 6.x). Not terribly > surprisingly, I'm running into the duplicate JAR issue, since > maven has the JARs on the classpath (or classworld) and the > WAR I need to feed Cargo also has the JARs. At least now I > remember why I've been running the container in a separate > JVM instance . . . > > Anyway, is anyone here running a similar setup and if so, how > are you working around this? One naïve approach is to change > the scope of the hivemind and tapestry JARs in the POM to > "provided", so they're not on the classpath, but then they > won't get added to the packaged WAR either. I've been at > this one for a bit now, so any help would be appreciated. > > Thanks, > Kevin > > --------------------------------------------------------------------- > 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]
