[MJAR-296] No way to suppress default excludes in maven-jar-plugin

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.4.0
• Assignee: Slawomir Jaranowski
• Reporter: G.Vaysman
• Created: 28/Sep/23 15:56
• Updated: 09/Apr/24 21:03
• Resolved: 09/Apr/24 21:00

Description

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:

1. The jar plugin skips adding the */ChangeSet/* files
2. The resources plugin is configured not to skip (addDefaultExcludes) and behaves properly

Issue Links

• relates to: MJAR-265 Resources not copied
• links to: GitHub Pull Request #67