[
http://jira.codehaus.org/browse/MWAR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MWAR-227:
---------------------------------
Priority: Major (was: Critical)
Issue Type: New Feature (was: Bug)
If you read the documentation, the <packagingExcludes> parameter is only
available for the war goal. Changing from bug to new feature.
http://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
> packaged (war:war) and exploded (war:expanded) webapps have different content
> -----------------------------------------------------------------------------
>
> Key: MWAR-227
> URL: http://jira.codehaus.org/browse/MWAR-227
> Project: Maven 2.x WAR Plugin
> Issue Type: New Feature
> Affects Versions: 2.1-beta-1
> Reporter: Kevin Wright
>
> Specifically, when using
> <packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes>, the jars are
> correctly excluded from the packaged form of the war, but still present in
> the exploded form.
> Both forms should have identical content and should be totally
> interchangable. This also means that there is no possible way to exclude
> jars from an exploded webapp.
> As a workaround, I also attempted this:
> {code:xml}
> <resource>
> <excludes>
> <exclude>WEB-INF/lib/*.jar</exclude>
> </excludes>
> </resource>
> {code}
> But just got an exception thrown for my efforts...
--
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
