I'm using Tomcat 5.5 which doesn't support EAR files. I think a move to a J2EE application server might be a good idea for the future but in the short term I'm going to use Tomcat.
Steve Vangasse www.boardshop.co.uk 0870 0600 688 -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 24 March 2007 00:15 To: Maven Users List Subject: Re: War plugin question Any reason you're not just packaging it all up in an EAR? Wayne On 3/23/07, Steve Vangasse <[EMAIL PROTECTED]> wrote: > The assembly plugin certainly seems to be the solution. > > My project is multi module; a module for each webapp and a module for the > shared library. I've been trying to write an assembly descriptor in the > parent module that copies all the jar files from each webapp module (that > would normally get copied into WEB-INF/lib) into a directory (I use > warSourceExcludes to stop the jars going to WEB-INF/lib). The examples on the > maven site don't seem to cover this kind of situation - has anyone attempted > anything like this? > > Thanks, > > Steve > > > -----Original Message----- > From: Kalle Korhonen [mailto:[EMAIL PROTECTED] > Sent: 20 March 2007 20:10 > To: Maven Users List > Subject: Re: War plugin question > > Re-design your applications so that common classes are in a jar, and include > the jars your want to share in your war with scope provided. Then, use the > assembly plugin to deploy the provided jars to shared/lib. We use a similar > approach and it works well. > > Kalle > > > On 3/20/07, Steve Vangasse <[EMAIL PROTECTED]> wrote: > > > > I actually have 2 webapps shared across multiple contexts that share > > a common library. When this library is built I've made an ant plugin > > that copies the library jar and all it's dependencies to Tomcat's > > common/lib directory. So I'm already using the provided scope for > > some jars used by the webapps that are in Tomcat's common/lib. > > > > Each webapp then has it's own dependencies (struts, jsf etc.) built > > straight into it's WEB-INF/lib directory and it's class files to > > WEB-INF/classes. This works fine but get's tight on memory when more > > and more contexts are running due to the webapp class loader. > > > > I'm really looking for a way to build any compile scoped jars > > straight into Tomcat's shared/lib along with the generated class > > files to shared/classes. > > > > Something like a "destination directory" setting in the war plugin > > would do the trick but I couldn't find one. Any ideas? > > > > Thanks again, > > > > Steve > > > > > > > > -----Original Message----- > > From: Rémy Sanlaville [mailto:[EMAIL PROTECTED] > > Sent: 20 March 2007 09:56 > > To: Maven Users List > > Subject: Re: War plugin question > > > > Hi Steve, > > > > Look at the provided scope for yours dependencies. > > > > http://maven.apache.org/guides/introduction/introduction-to-dependen > > cy > > -mechanism.html > > > > HTH, > > > > Rémy > > > > > > 2007/3/20, Steve Vangasse <[EMAIL PROTECTED]>: > > > > > > My application uses a war file that is shared by multiple contexts > > > within Tomcat. I'm using the Maven2 War plugin to build the war file. > > > At present the generated class files and the jar files used by the > > > application are put inside the war file's WEB-INF/lib and > > > WEB-INF/classes directories. I would like to be able to decrease > > > the memory footprint by putting these files into Tomcat's > > > shared/lib and shared/classes directories. Does anyone know of a > > > way that this can be done? > > > > > > Thanks, > > > > > > Steve > > > > > > > > > > > > > -------------------------------------------------------------------- > > - 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]
