[ 
https://jira.codehaus.org/browse/MECLIPSE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304339#comment-304339
 ] 

David Ledanseur commented on MECLIPSE-167:
------------------------------------------

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


                
> .component assumes all dependencies should be packaged in WAR
> -------------------------------------------------------------
>
>                 Key: MECLIPSE-167
>                 URL: https://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.patch, 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, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to