apache / apache/maven-assembly-plugin
[MASSEMBLY-1002] Assembly fails to include directories when they are symbolic links
- Dominant language
- Java
- Stars
- 110
- Forks
- 75
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 10
Description
**[Jimisola Laursen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER281352)** opened **[MASSEMBLY-1002](https://issues.apache.org/jira/browse/MASSEMBLY-1002?redirect=false)** and commented
Assembly fails to include directories when they are symbolic links.
E.g.
If the directory "${project.basedir}/target/surefire-reports" is a symbolic link to another directory then the following fileset will not work.
```java
${project.basedir}/target/surefire-reports
/test_results/surefire
*.*
```
However, if the directory "${project.basedir}/target/surefire-reports" is an actual directory (and not a symlinj ) and the files in that directory are symbolic links then it works as expected.
I'm guessing that this might not be a bug in this plugin but rather Maven Resources.
There is a related [issue](https://issues.apache.org/jira/browse/MRESOURCES-237) in terms of being about symlinks, but that ticket is about preserving symbolic links or not which in not the case here.
---
**Affects:** 3.6.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported fileset behavior in maven-assembly-plugin 3.6.0, using a directory path that is a symbolic link and comparing it with an actual directory containing symbolic-link files. Trace the fileset handling to determine where the linked directory is skipped. Done means files from the linked directory are included as expected.
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
- 35/100