Rather than creating static zips in each module directory, why not use a
fileSet to refer to the module subdirs that contain the static content, and
create the single static zip from the top level? Then, if you want that
static content in a zip that's in addition to the war and jar files in your
distro zip, you *might* be able to put the static assembly fragments in a
separate assembly descriptor, bound to the lifecycle in an earlier phase (in
a separate <execution/>). Then, simply refer to the output of that static
assembly when you create the other one that contains the wars, etc.
Does that make sense?
-john
On 3/28/07, mraible <[EMAIL PROTECTED]> wrote:
I've managed to get my WARs and ZIPs into the same release ZIP using the
following assembly descriptor. However, I'd like to combine the two zips
into a single zip. Is this possible with the maven-assembly-plugin or do
I
need to resort to Ant for that?
<assembly>
<id>bin</id>
<formats>
<format>zip</format>
</formats>
<moduleSets>
<moduleSet>
<includes>
<include>com.foo:foo-core:jar</include>
<include>com.foo:foo-war1:war</include>
<include>com.foo:foo-war2:war</include>
</includes>
<binaries>
<unpack>false</unpack>
</binaries>
</moduleSet>
</moduleSets>
<fileSets>
<fileSet>
<directory>sites/war1/target</directory>
<outputDirectory></outputDirectory>
<includes>
<include>*.zip</include>
</includes>
</fileSet>
<fileSet>
<directory>sites/war2/target</directory>
<outputDirectory></outputDirectory>
<includes>
<include>*.zip</include>
</includes>
</fileSet>
</fileSets>
</assembly>
If I do need to resort to Ant, is it a good idea to configure this
assembly
in my root pom.xml? While this seems the simplest way, creating an
"assembly" module seems like it might give me the ability to create my
release zip after everything else has been executed. With the root
pom.xml,
I believe install happens before any modules are built, so it'd be tough
to
hook into the lifecycle to build the release zip.
Thanks,
Matt
mraible wrote:
>
> I'm trying to use the assembly plugin to package up WARs from a bunch of
> sub-projects. My goal is to get a target/release.zip after running "mvn
> package" from the top-level directory.
>
> I have this working when I run "mvn package assembly:assembly", but I'd
> like to make it work for "mvn package" of my root pom.xml. Is it
possible
> to use an <execution> to make this work?
>
> 2ndly, I'm using the assembly plugin to zip up static content in my WARs
> so it can be deployed to an external webserver. I have it working
> (details at
> http://www.nabble.com/Re%3A-Packaging-up-images-p9699901s177.html), but
1)
> I can't get one WAR to depend on these zipped artifacts and 2) I can't
> figure out how to get the top-level assembly to include the zip files.
>
> Currently, there are zip files created by an assembly in each WAR
project.
> In an ideal world, I could combine these into one static-content.zip in
> the zip that's produced by the root assembly. Here's the bin.xml I'm
> using for my top-level assembly:
>
> <assembly>
> <id>bin</id>
> <formats>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <moduleSets>
> <moduleSet>
> <includes>
> <include>com.company:webapp1:war</include>
> <include>com.company:webapp2:war</include>
> </includes>
> <binaries>
> <outputDirectory></outputDirectory>
> <unpack>false</unpack>
> </binaries>
> </moduleSet>
> </moduleSets>
> </assembly>
>
> Thanks,
>
> Matt
>
--
View this message in context:
http://www.nabble.com/Using-the-assembly-plugin-to-package-up-WARs-and-ZIPs-tf3477317s177.html#a9718419
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
