Message-
From: Michael Horwitz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 15, 2006 9:31 AM
To: Maven Developers List
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [appfuse-dev] War plugin overlays: New plugin to handle
transitive dependencies
It would be nice! In AppFuse only one wa
dependencies
are resolved isn't it?
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 1:56 PM
To: [EMAIL PROTECTED]
Cc: dev@maven.apache.org
Subject: Re: [appfuse-dev] War plugin overlays: New plugin to handle
transitive dependencies
6 PM
To: [EMAIL PROTECTED]
Cc: dev@maven.apache.org
Subject: Re: [appfuse-dev] War plugin overlays: New plugin to handle
transitive dependencies
Just some thoughts on enhancements:
It'd be nice if we could 1) get this into the war plugin and 2) add 3
different modes:
1. Default - the way t
ad your point 2)
For what i've experienced, the dependencies of a WAR
may only be derived if the actual project itself is of
type WAR too.
As opposite, the dependencies from a WAR imho must not
be derived if the actual project is e.g. of type EAR.
Do we need any further distinction?
lg,
strub
Just some thoughts on enhancements:
It'd be nice if we could 1) get this into the war plugin and 2) add 3
different modes:
1. Default - the way things are now, where dependencies aren't
inherited. This would allow backwards compatibility and not suprise
anyone.
2. Include Dependencies - exclud
