[MECLIPSE-167] .component assumes all dependencies should be packaged in WAR

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Component/s: WTP support
• Assignee: Robert Scholte
• Reporter: Shelley
• Created: 06/Oct/06 11:32
• Updated: 25/Dec/15 11:49
• Resolved: 25/Dec/15 11:49

Description

Our applications are packaged such that the JAR dependencies are packaged within the EAR, not the WARs. The dependencies are listed in the WAR in order to generate the MANIFEST.MF class-path entries, and to add compile dependencies to the .classpath. These dependencies are excluded from the packaged WAR, however, via the maven-war-plugin's warSourceExcludes configuration: <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes> since they reference the EAR. [Related: MWAR-9]

The Eclipse Plugin WTP configuration file generation currently assumes that all WAR project dependencies should be packaged and deployed in the WAR. Each dependency is listed as a "dependent-module" with a deploy-path of "/WEB-INF/lib" in the .component file.

This causes the dependencies to be duplicated and packaged in the EAR and in every WAR when the project is published to an app server.

The eclipse-plugin should expose additional WTP configuration or read the war-plugin's configuration in order to exclude these dependencies from being packaged and deployed within the WAR.

Issue Links

• relates to: MECLIPSE-184 Ear utility-jar are put in WEB-INF/lib of the wtp ear
• relates to: MWAR-9 WAR plugin should support minimal WARs for inclusion within an EAR