Thanks for the info on copyDependencies. That got the dependencies copied to a folder, which was one step closer. I needed them in a single artifact though, which led me to look at the assembly plugin. Using maven-assembly-plugin with <dependencySet> gives me exactly what I wanted.
On Fri, Nov 21, 2008 at 12:54 PM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > have a look at the copyDependencies goal of the maven-dependency-plugin (or > it might be the copy-dependencies goal) > > Sent from my iPod > > > On 21 Nov 2008, at 19:23, "Andrew Goktepe" <[EMAIL PROTECTED]> > wrote: > > Before I look into writing a custom plugin: is there any way to get Maven >> to >> produce an artifact (zip?) containing the dependencies with scope >> "provided"? >> >> Most of the jar files required by our web app will be provided by Tomcat >> outside of the war file. But since I also need to be the one to provide >> these jars, it would be ideal if I could have Maven produce them based on >> declared scope in the POM files. Without this, we are sure to see >> mismatches in compile vs runtime library versions over time. >> >> -Andrew >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
