Project organization question.

["David C. Hicks" <dh...@i-hicks.org>]

Hi folks,

Our project current produces a WAR, but we also have an assembly that 
combines that WAR with a few other "release" files.  I realize that a 
project should really only have a single artifact.  So, I'm wondering if 
this is a good place to break a project into a couple of modules, then 
let one of those modules be the "assembly" artifact??  It's the assembly 
that I eventually want to release for "public" consumption.

Thanks in advance,
Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Project organization question.

[Heinrich Nirschl <he...@gmail.com>]

On Thu, Nov 6, 2008 at 9:46 PM, David C. Hicks <dh...@i-hicks.org> wrote:
> Hi folks,
>
> Our project current produces a WAR, but we also have an assembly that
> combines that WAR with a few other "release" files.  I realize that a
> project should really only have a single artifact.  So, I'm wondering if
> this is a good place to break a project into a couple of modules, then let
> one of those modules be the "assembly" artifact??  It's the assembly that I
> eventually want to release for "public" consumption.

Yes, I would set up 3 maven projects (assuming that no other modules
are needed):
- the WAR
- the assembly (which depends on the WAR)
- a common parent of the two (packaging type POM, with the other two
projects as modules)

With this structure, you can still build all your artifacts with a
single maven command. Furthermore, you have a place to define common
properties or dependency versions by putting these settings into the
parent.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org