Is there a way to detect when the dependencies of two war artifacts are
inconsistent with respect to packaged jar versions?
E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed
where an inconsistent dependency on abc-1.0.1.jar is also defined.
The resulting war will contain
mvn dependency:tree should let you see that there are 2 of the same
jars, but it won't "alert" you.
A better solution might be to use a section in
the parent pom of both modules in which you specify the jar versions.
That way you won't have the problem of using different versions in
diff
dependency:tree doesn't currently show overlaid war jars. The war
overlay concept is conceptually outside of the normal dependency
mechanism, hence the possibility of ending up with two versions of the
same dependency.
Anyone aware of an issue about this? The war plugin should really
fail the bu
far as I can tell,
>>> the subsequent behavior is indeterminate.
>>>
>>>
>>>
>>> Brad
>>>
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For
2009/5/12 Brad Harper :
> I was hoping to hear someone say that the war file should generate an error
> or fail.
>
> In our case, we have multiple versions of a general 'platform', each
> represented by a war artifact. Derivative wars artifacts are built with
> customizations and tailorings using a
Harper, Brad wrote at Montag, 11. Mai 2009 21:55:
> Is there a way to detect when the dependencies of two war artifacts are
> inconsistent with respect to packaged jar versions?
>
>
>
> E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed
> where an inconsistent dependency on
I didn't see one, so I added one. Refer to
http://jira.codehaus.org/browse/MWAR-194.
Thanks.
Brad
-Original Message-
From: Mark Hobson [mailto:markhob...@gmail.com]
Sent: Wednesday, May 13, 2009 3:37 AM
To: Maven Users List
Subject: Re: War Overlays and Conflicting Jars
2009/5/12
and Conflicting Jars
Is there a way to detect when the dependencies of two war artifacts are
inconsistent with respect to packaged jar versions?
E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed
where an inconsistent dependency on abc-1.0.1.jar is also defined.
The
