[
https://jira.codehaus.org/browse/MEAR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350042#comment-350042
]
Mark Howard commented on MEAR-182:
----------------------------------
We're also having issues with this - maven-ear-plugin 2.8 didn't modify the
classpath, so this is a regression for us. We also can't get the classpath to
work with weblogic (probably relating to using transitive dependencies), so are
currently stuck with the slow 2.8 release.
> Skinny WAR's - Skip Class-Path Modification in Manifest
> -------------------------------------------------------
>
> Key: MEAR-182
> URL: https://jira.codehaus.org/browse/MEAR-182
> Project: Maven Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Mario Däpp
> Fix For: 2.10
>
> Attachments: MEAR-182-patch.txt
>
>
> From Java EE 5, a library directory may be specified in the application.xml
> (element library-directory). The Maven EAR Plugin already supports this for
> generating the application.xml (value of property defaultLibBundleDir).
> The Java EE 5 specification mandates that all JAR files contained in the
> library directory be made available to all modules within the EAR file (cf.
> chapter EE.8.2.1 Bundled Libraries, section 2).
> If one specifies both the skinnyWars (value = true) and defaultLibBundleDir
> parameters, the libraries will be removed from the WAR and copied to the
> defaultLibBundleDir. They will also be added to the Class-Path in the WAR
> files manifest. This is unnecessary as per the Java EE 5 specification. Even
> worse, it breaks my EAR on WebLogic (classloading issues).
> I therefore propose the following improvement to the skinny WAR's
> functionality: If the Java EE version is 5 or greater and the
> defaultLibBundleDir has been specified, the Class-Path in the WAR's manifest
> should remain unchanged.
> I've created a corresponding patch and integration test.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
