Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1-beta-1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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:
<resource> <excludes> <exclude>WEB-INF/lib/*.jar</exclude> </excludes> </resource>
But just got an exception thrown for my efforts...
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