On 21 Mar 2007, at 07:04, Stephane Nicoll wrote:
Hi,
On 3/21/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Will the use of this new overlay cause the transitive dependencies
of the overlayed wars to be resolved and included? I currently
construct wars that I intend to be used as overlays by excluding
all the jars. I do this to avoid conflicts but also to reduce the
size in the repository. Unfortunately because I'm using a very old
version of mwar, I have to manually keep my war project
dependencies synchronized. If these transitive dependencies from
the wars are automatically pulled in, then I think it's safe to
also exclude WEB-INF/lib by default from the overlays. I think
we'll have an excellent solution at that point.
The proposition sticks to a simple overlay which does not resolve the
transitive dependencies, that's a very good point. We could even put a
default exclude on WEB-INF/* for overlays that are not the current
build (?). This will also solves the issues of people having multiple
time the same dep with a different minor versions in the resulting
war.
Erm, does that not mean that all classes from other wars will be
omitted?
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
