G.Vaysman created MJAR-296:
------------------------------
Summary: No way to suppress default excludes in maven-jar-plugin
Key: MJAR-296
URL: https://issues.apache.org/jira/browse/MJAR-296
Project: Maven JAR Plugin
Issue Type: Bug
Affects Versions: 3.3.0
Reporter: G.Vaysman
Attachments: jar-default-excludes.zip
With the default excludes being expanded further (see
org.codehaus.plexus.util.AbstractScanner.{*}_DEFAULTEXCLUDES_{*}), a resource
directory **/ChangeSet/** will never be included in the JAR artifact.
Some plugins (maven-resources-plugin, maven-assembly-plugin) already allow
suppressing the exclusion, but not the maven-jar-plugin. Code analysis of the
JarMojo -> DirectoryScanner call path confirms that there is no way to affect
the FileSet configuration.
Again, with ever expanding list of *_DEFAULTEXCLUDES,_* this, on our opinion,
is quite detrimental, and due to backward compatibility, changing
resource/package path (say, to ChangeSet2) is not an option.
I am attaching a very simple project that shows two things:
# The jar plugin skips adding the **/ChangeSet/** files
# The resources plugin is configured not to skip (addDefaultExcludes) and
behaves properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
