If you have a multi-module build, I'd consider Wendy's suggestion a best practice. However if you just happen to have a single module and want to avoid creating another one (and a parent for them) you can use dependency plugin's copy goal to pull the jar in and put it somewhere (like target/lib), then use assembly's fileset to include it into the assembly.
Kalle On Fri, Sep 4, 2009 at 12:08 PM, Wendy Smoak<[email protected]> wrote: > On Fri, Sep 4, 2009 at 12:02 PM, Jim Collings<[email protected]> wrote: >> Is there any way to do this? The jar in question is not part of my >> build but is part of my assembly as it needs to be installed into the >> web container by the installation script. >> I've had one suggestion so far that I should create a separate module >> for getting the jar but I'll need more details. The jar is never >> downloaded and after all why would it be? There isn't any code in the >> module in question. It just makes an empty jar file. It has a pom and >> a manifest and that's it. > > Add this jar as a <dependency> of the separate module that builds your > assembly. The packaging of this module would be 'pom'. Maven should > resolve the dependencies and download it for you, and you can include > it in your assembly. > > -- > Wendy > > --------------------------------------------------------------------- > 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]
