apache / apache/maven-assembly-plugin
[MASSEMBLY-852] <directoryMode> permissions are lost if <include> is present
- Dominant language
- Java
- Stars
- 110
- Forks
- 75
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 10
Description
**[Anton](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=anton.kabachkov)** opened **[MASSEMBLY-852](https://issues.apache.org/jira/browse/MASSEMBLY-852?redirect=false)** and commented
Used next descriptor:
```xml
test
zip
false
bin
bin-include
*
700
700
bin
bin-no-include
700
700
```
For both **** same **directoryMode** is set, but for case where **** pattern is present directory permissions are broken.
Listing:
```
$ zipinfo target/testpom-1.0.0.zip
Archive: target/testpom-1.0.0.zip
Zip file size: 502 bytes, number of entries: 4
drwxr-xr-x 2.0 unx 0 b- stor 17-Apr-19 17:48 bin-include/
drwx------ 2.0 unx 0 b- stor 17-Apr-19 15:48 bin-no-include/
-rwx------ 2.0 unx 0 bl defN 17-Apr-19 15:48 bin-include/testfile
-rwx------ 2.0 unx 0 bl defN 17-Apr-19 15:48 bin-no-include/testfile
```
---
**Affects:** 3.0.0
**Attachments:**
- [test.rar](https://issues.apache.org/jira/secure/attachment/12864025/test.rar) (_862 bytes_)
**Remote Links:**
- [GitHub Pull Request #37
](https://github.com/apache/maven-assembly-plugin/pull/37)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the assembly descriptor in the report and compare the two fileSets, one with an include pattern and one without. Reproduce the ZIP output with zipinfo; done means both generated directories preserve the configured directoryMode of 700, while accounting for the linked Pull Request #37.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100