maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mario Däpp (JIRA) <>
Subject [jira] (MEAR-182) Skinny WAR's - Skip Class-Path Modification in Manifest
Date Mon, 16 Jun 2014 03:50:11 GMT


Mario Däpp commented on MEAR-182:

Sounds good. This fix will be much appreciated.

> Skinny WAR's - Skip Class-Path Modification in Manifest
> -------------------------------------------------------
>                 Key: MEAR-182
>                 URL:
>             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

View raw message