[
http://jira.codehaus.org/browse/MECLIPSE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Baker updated MECLIPSE-167:
-----------------------------------
Attachment: MECLIPSE-167.zip
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
> .component assumes all dependencies should be packaged in WAR
> -------------------------------------------------------------
>
> Key: MECLIPSE-167
> URL: http://jira.codehaus.org/browse/MECLIPSE-167
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> Reporter: Shelley Baker
> Priority: Critical
> Attachments: MECLIPSE-167.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
