maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MWAR-178) war plugin documentation and probably implementation is unaware of javaee 5
Date Sun, 15 Mar 2015 22:38:18 GMT

     [ https://jira.codehaus.org/browse/MWAR-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl-Heinz Marbaise closed MWAR-178.
------------------------------------

    Resolution: Won't Fix

If you have any objections don't hesitate to reopen the issue.

> war plugin documentation and probably implementation is unaware of javaee 5
> ---------------------------------------------------------------------------
>
>                 Key: MWAR-178
>                 URL: https://jira.codehaus.org/browse/MWAR-178
>             Project: Maven WAR Plugin
>          Issue Type: New Feature
>            Reporter: David Jencks
>
> The example I'm aware of:
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html talks about
using the war's manifest.mf classpath to include jars in the ear in the war module's classloader.
 In ee5, there's a ear lib directory: everything in that is automatically included in the
ear level classloader, which is certainly available to every war, most likely by being a parent
classloader to the war classloader.  One consequence of this is that using the manifest classpath
in a 1.4 container will likely result in each war getting separate copies of the lib jar classes
whereas the ee5 lib directory will result in shared classes.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message