apache / apache/maven-assembly-plugin
[MASSEMBLY-759] tar outputs missing entries for target directory.
- Dominant language
- Java
- Stars
- 110
- Forks
- 75
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 10
Description
**[mike duigou](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bondolo)** opened **[MASSEMBLY-759](https://issues.apache.org/jira/browse/MASSEMBLY-759?redirect=false)** and commented
> \ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
> \tarball\
> \
> \tar\
> \tbz2\
> \
> \false\
> \
> \
> \./lib\
> \0755\
> \true\
> \false\
> \runtime\
> \
> \*:javaee-web-api\
> \
> \
> \
> \
Does not output a tar record for the created "lib"directory, just for the entries under it:
> ....
> -rw-r--r-- 0 mike staff 60686 29 Dec 13:19 lib/commons-logging-1.1.1.jar
> ....
The only alternative seems to be to create a lib directory somewhere and use a fileset to copy it over before the dependencySet
---
**Affects:** 2.5.3
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the assembly configuration shown in the report, using the dependency set with outputDirectory ./lib and tar/tbz2 formats. Inspect the archive-generation path to determine why the created lib directory has no tar record; done means the archive contains an entry for lib as well as its dependency files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100