Maven 2.x Eclipse Plugin

.component assumes all dependencies should be packaged in WAR

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: WTP support
  • Labels:
    None
  • Number of attachments :
    2

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

Improvement - An improvement or enhancement to an existing feature or task. MECLIPSE-184 Ear utility-jar are put in WEB-INF/lib of the wtp ear

  • Critical - Crashes, loss of data, severe memory leak.
  • Open - The issue is open and ready for the assignee to start work on it.

Improvement - An improvement or enhancement to an existing feature or task. MWAR-9 WAR plugin should support minimal WARs for inclusion within an EAR

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Arnaud Heritier added a comment -

Can you give us a sample about what we have to generate.
Or a little project as sample could be better (maven + eclipse generated files)

Show
Arnaud Heritier added a comment - Can you give us a sample about what we have to generate. Or a little project as sample could be better (maven + eclipse generated files)
Hide
Permalink
Shelley Baker added a comment -

The attached project provides some minimal project content/configuration to demonstrate this issue.

Execute "mvn install eclipse:eclipse" and examine the generated org.eclipse.wst.common.component files. Notice that the JAR dependencies are dependent-modules in both the EAR and WAR projects.

In the Maven build of these projects (outside of the IDE), the WAR would /not/ include the JARs, but rather, would only reference these JARs from the EAR (via the Manifest class-path).

The issue here is that the maven-eclipse-plugin should allow WTP configuration to exclude dependencies from the WEB-INF/lib, or infer this desired configuration based on the maven-war-plugin's configuration of a "skinny" war [1].

[1] http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html

Show
Shelley Baker added a comment - The attached project provides some minimal project content/configuration to demonstrate this issue. Execute "mvn install eclipse:eclipse" and examine the generated org.eclipse.wst.common.component files. Notice that the JAR dependencies are dependent-modules in both the EAR and WAR projects. In the Maven build of these projects (outside of the IDE), the WAR would /not/ include the JARs, but rather, would only reference these JARs from the EAR (via the Manifest class-path). The issue here is that the maven-eclipse-plugin should allow WTP configuration to exclude dependencies from the WEB-INF/lib, or infer this desired configuration based on the maven-war-plugin's configuration of a "skinny" war [1] . [1] http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
Hide
Permalink
David Ledanseur added a comment -

Here is a patch that allows excluding some artifacts from the WEB-INF/lib folder. It follows the given guideline :

http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html

i.e. dependencies marked as optional are excluded from the packaging

Show
David Ledanseur added a comment - Here is a patch that allows excluding some artifacts from the WEB-INF/lib folder. It follows the given guideline : http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html i.e. dependencies marked as optional are excluded from the packaging

People

  • Assignee:
    Unassigned
    Reporter:
    Shelley Baker
Vote (2)
Watch (4)

Dates

  • Created:
    Updated: