maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dieter König (JIRA) <>
Subject [jira] (MWAR-227) packaged (war:war) and exploded (war:expanded) webapps have different content
Date Wed, 12 Sep 2012 12:37:21 GMT


Dieter König commented on MWAR-227:

Huh? You are referencing the documentation. Is possibly the documentation of exploded goal
Create an exploded webapp in a specified directory."

How should this be understood?

By the way there is no need in functionality exploded goal provides ACTUALLY because the exploded
directory in that form is already generated during war:war processing. That's why i was also
assuming exploded would generate the "unpackaged" war and what indeed should be the truth.
> packaged (war:war) and exploded (war:expanded) webapps have different content
> -----------------------------------------------------------------------------
>                 Key: MWAR-227
>                 URL:
>             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, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message