[MEAR-17] Jar files packed in the EAR file should also be added to application.xml or manifest.mf

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Assignee: Stephane Nicoll
• Reporter: Kristoffer Peterhänsel
• Created: 24/Jan/06 09:41
• Updated: 07/Apr/15 18:37
• Resolved: 01/Aug/06 13:30

Description

While attempting to package an EAR for deployment on JBoss I have come across a (for me) major issue with the way this module works.

The issue is that there are a lot dependency jars included by default. That by itself isn't the problem. The problem is there is no way to include it in the classpath without defining all the dependencies again in the pom.xml for the EAR.

In an ideal world (for me) the jars would be an easy way to add the jars to the classpath since I want to include all I need in the EAR to make it as easy as possible to set up a depoyment environment.

There are really two options for how to do that. Either the jar files are added to the generated Manifest.MF file or else there should be a simple option to include all packed jar files to the application.xml. Both should (AFAIK) work in any standard-compliant container.

The option of putting all the jar files in APP-INF/lib only works on Weblogic.

Issue Links

• relates to: MWAR-21 Need a way to include limited set of webapp's dependencies
• relates to: MWAR-9 WAR plugin should support minimal WARs for inclusion within an EAR