[MEAR-182] Skinny WAR's - Skip Class-Path Modification in Manifest

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 2.10
• Flags: Patch
• Assignee: Karl Heinz Marbaise
• Reporter: Mario Däpp
• Created: 03/Apr/14 13:20
• Updated: 20/Dec/20 10:39
• Resolved: 12/Dec/14 14:19

Description

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.

Issue Links

• causes: MEAR-292 skipClassPathModification option should prevent adding Class-Path entry into MANIFEST.mf
• links to: GitHub Pull Request #28