apache / apache/maven-assembly-plugin

[MASSEMBLY-505] Feature Request: useStrictFiltering option for FileSets

Open
#670 10 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
110
Forks
75
Avg merge
12h 54m
Merged PRs (30d)
10

Description

**[John Dennis Casey](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdcasey)** opened **[MASSEMBLY-505](https://issues.apache.org/jira/browse/MASSEMBLY-505?redirect=false)** and commented

**NOTE:** This is a clone of MASSEMBLY-488. The original issue will be closed Won't Fix, since the plexus-utils class DirectoryScanner, which is the core of the FileSet functionality, doesn't support strict include/exclude filtering.

This issue is a feature request to have that added.

---

I'm trying to turn on useStrictFiltering in a fileSet in an assembly
descriptor, but maven doesn't fail when the file does not exist. Here
is an example of what the assembly descriptor looks like:

\\
\
\tar.gz\
\
\
\
\true\
\src/main\
\
\nonexistant.txt*\
\
\
\
\
Running "mvn package" happily produces a tarball with no indication that anything is wrong.

---

**Affects:** 2.2

**Attachments:**
- [fail_strictfiltering.zip](https://issues.apache.org/jira/secure/attachment/12714050/fail_strictfiltering.zip) (_1.79 kB_)

**Issue Links:**
- [MASSEMBLY-779](https://issues.apache.org/jira/browse/MASSEMBLY-779) It would be useful to be able to make the assembly plugin fail on errors
(_**"blocks"**_)
- [MASSEMBLY-1018](https://issues.apache.org/jira/browse/MASSEMBLY-1018) Fix examples about useStrictFiltering

- [MASSEMBLY-488](https://issues.apache.org/jira/browse/MASSEMBLY-488) restrict useStrictFiltering option to DependencySets
(_**"supercedes"**_)

11 votes, 13 watchers

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the assembly descriptor's FileSet handling and the plexus-utils DirectoryScanner, which the issue identifies as the core limitation; use fail_strictfiltering.zip and run the shown mvn package scenario. Done means a missing strict include causes the Maven Assembly Plugin build to fail for FileSets, rather than silently producing an incomplete tarball.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.