jira-importer opened a new issue, #190:
URL: https://github.com/apache/maven-war-plugin/issues/190

   **[Dirk 
Olmes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=d...@xanthippe.ping.de)**
 opened 
**[MWAR-21](https://issues.apache.org/jira/browse/MWAR-21?redirect=false)** and 
commented
   
   I need a way to pack a war that includes only a limited set of the webapp's 
dependencies. We're deploying in mainly two different environments: for 
testing, the webapp runs standalone and thus needs to include all its 
dependencies in the war. For production we deploy the webapp into a JBoss 
server that has all the dependencies already installed.
   
   I've modified AbstractWarMojo in the following way: 1) allow to specify 
dependencyIncludes an dependencyExcludes (as lists) 2) upon building the war, 
each dependency is checked against the excludes and the includes and will be 
added to the war accordingly.
   
   While this patch may not be the best way to to it, it clearly shows my 
requirements.
   
   
   ---
   
   **Attachments:**
   - 
[AbstractWarMojo.diff](https://issues.apache.org/jira/secure/attachment/12720626/AbstractWarMojo.diff)
 (_3.16 kB_)
   - 
[AbstractWarMojo.patch](https://issues.apache.org/jira/secure/attachment/12720641/AbstractWarMojo.patch)
 (_10.77 kB_)
   - 
[MWAR-21-workaround.patch](https://issues.apache.org/jira/secure/attachment/12720604/MWAR-21-workaround.patch)
 (_4.38 kB_)
   
   **Issue Links:**
   - [MEAR-17](https://issues.apache.org/jira/browse/MEAR-17) Jar files packed 
in the EAR file should also be added to application.xml or manifest.mf
   
   - [MWAR-9](https://issues.apache.org/jira/browse/MWAR-9) WAR plugin should 
support minimal WARs for inclusion within an EAR
   
   
   1 votes, 10 watchers
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to