[
http://jira.codehaus.org/browse/MWAR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111241
]
Joerg Schaible commented on MWAR-33:
------------------------------------
We fight with this problem also. Currently we use warExcludes and redeclare all
the deps. The best solution though might be to introduce a war-client.jar
similar to an ejb-client. The war-client.jar would contain all classes and - as
attached artifact - it would provide the transitive deps. With such an artifact
you could use a dependent war as overlay and exclude anything from WEB-INF/lib
and WEB-INF/classes and declare the war-client as additional dep. Since the
war-client is a jar, you'll inherit then all the transitive deps.
> jars with differents versions can be in WEB-INF/lib with war as dependencies
> ----------------------------------------------------------------------------
>
> Key: MWAR-33
> URL: http://jira.codehaus.org/browse/MWAR-33
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Environment: all
> Reporter: Olivier Lamy
> Assignee: Stephane Nicoll
> Fix For: 2.1-alpha-2
>
> Original Estimate: 15 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> My pom has the following dependencies :
> - log4j:log4j:1.2.13
> - a war with log4j:log4j:1.2.11 included
> Result the two jars are in WEB-INF/lib.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
