Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1.1
-
Fix Version/s: None
-
Component/s: overlay
-
Labels:None
-
Number of attachments :
Description
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
The deprecation should be simply reverted. Even the plugin overlay documentation (http://maven.apache.org/plugins/maven-war-plugin/overlays.html) explicitly refers dependentWarExcludes and dependentWarIncludes as the only possibility to make global settings in a plugin management section that is inherited in multiple projects. There is no equivalent possible with overlays/overlay/excludes or overlays/overlay/includes and actually it is also not necessary to introduce something else for a mechanism that is working properly.