[
https://jira.codehaus.org/browse/MWAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane StClair updated MWAR-253:
-------------------------------
Attachment: war-deps.tar
Example project attached (also at https://github.com/srstclair/war-deps) shows
the current behavior, meaning that transitive dependencies of the war
dependency are not available on the classpath (the war-deps-via-war module's
tests fail). I agree with Maarten that transitive dependencies should be
resolved for war dependencies.
Currently the best workaround I can come up with is to declare a second
dependency on the war's pom, which does add transitive dependencies to the
classpath (see war-deps-overlay). Is that the recommended approach?
> Inherit dependencies from a WAR type dependency when it is overlayed.
> ---------------------------------------------------------------------
>
> Key: MWAR-253
> URL: https://jira.codehaus.org/browse/MWAR-253
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: Maarten Billemont
> Attachments: war-deps.tar
>
>
> When WAR artifact B depends on WAR artifact A, and also defines an overlay of
> A, B should inherit all A's dependencies.
> This issue is related to MNG-1991, but can be resolved without much
> discussion as it's unrelated to skinny WARs and such.
> Classes in B are guaranteed to have runtime access to all A's declared
> dependencies when A is an overlay of B.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
