You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/12 21:12:42 UTC
[jira] [Closed] (MWAR-227) packaged (war:war) and exploded
(war:expanded) webapps have different content
[ https://issues.apache.org/jira/browse/MWAR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MWAR-227.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> packaged (war:war) and exploded (war:expanded) webapps have different content
> -----------------------------------------------------------------------------
>
> Key: MWAR-227
> URL: https://issues.apache.org/jira/browse/MWAR-227
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)