maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luca Li Greci <>
Subject Re: Understanding Assembly Plugin
Date Mon, 21 Sep 2009 21:00:18 GMT
Hi Neil,

I usually add a project for the distribution so that I can decouple the
"build logic"  from the modules. In the parent I define the assembly plugin
and in this distribution module I write the assembly under

Using this approach will avoid weird situation where one module (I assume
the persistence) needs to be built before one other (I assume the service)

To write my assembly descriptor I've read

and I used FileSets and dependencySets.

Best regards


2009/9/21 Neil Chaudhuri <>

> I have 4 poms:
> 1) parent, which has common dependencies and configuration shared by
> children
> 2) persistence, which packages a jar and is a child of parent
> 3) services, which packages a war, is a child of parent, and has
> persistence as a dependency
> 4) logging, which packages a jar that is a dependency of both persistence
> and services but is not part of the parent-child relationship shared by the
> others
> I want to use the Maven assembly plugin so that I can build a war file in
> one command line execution. This means packaging and installing logging,
> then packaging and installing persistence, then packaging services.
> Can you tell me where I should define my assembly plugin configuration? At
> the parent? Also, what would it look like roughly?
> Thanks.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Victor Hugo wrote, “The future has many names: For the weak, it means the
unattainable. For the fearful, it means the unknown. For the courageous, it
means opportunity.”

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message