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/03/09 10:33:40 UTC

[jira] [Updated] (MWAR-257) Remove deprecation of dependentWarExcludes, since there is no alternative on global level

     [ https://issues.apache.org/jira/browse/MWAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MWAR-257:
--------------------------------
    Summary: Remove deprecation of dependentWarExcludes, since there is no alternative on global level  (was: dependentWarExcludes is deprecated but )

> Remove deprecation of dependentWarExcludes, since there is no alternative on global level
> -----------------------------------------------------------------------------------------
>
>                 Key: MWAR-257
>                 URL: https://issues.apache.org/jira/browse/MWAR-257
>             Project: Maven WAR Plugin
>          Issue Type: Bug
>          Components: overlay
>    Affects Versions: 2.1.1
>            Reporter: dool
>
> 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)