[
https://issues.apache.org/jira/browse/MWAR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186104#comment-15186104
]
Joerg Schaible commented on MWAR-368:
-------------------------------------
There's no alternative to dependentWarExcludes. It's the only way to define
defaults on a global level.
> CLONE - dependentWarExcludes is deprecated but
> -----------------------------------------------
>
> Key: MWAR-368
> URL: https://issues.apache.org/jira/browse/MWAR-368
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
> Affects Versions: 2.1.1
> Reporter: Joerg Schaible
> Assignee: Karl Heinz Marbaise
>
> Hello,
> DependentWarExcludes is marked as deprecated. Documentation says to use
> <overlay>/<excludes> instead.
> But it seems to me that it is not possible to get the same behaviour with
> <overlay>/<excludes> as in this case we have to provide groupIds and
> artifactIds.
> Maybe this behaviour could be reproduced when setting both groupId and
> artifactId to * as below :
> <overlays>
> <overlay>
> <excludes>
> <groupId>*</groupId>
> <artifactId>*</artifactId>
> <exclude>**/*</exclude>
> </excludes>
>
> </overlay>
> </overlays>
> By the way, I found this, by looking for a way to disable overlay. The
> workaround I thought was configuring your plugin to exclude every files when
> overlaying.
> I think it would be nice to have a configuration parameter for that.
> Many thanks,
> Dool
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
