apache / apache/maven-assembly-plugin
[MASSEMBLY-763] build failure when running "package assembly:single" on a project
- Dominant language
- Java
- Stars
- 110
- Forks
- 75
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 10
Description
**[Fabien](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fabien-dalai)** opened **[MASSEMBLY-763](https://issues.apache.org/jira/browse/MASSEMBLY-763?redirect=false)** and commented
Following a question opened on stackoverflow (see here http://stackoverflow.com/questions/29199748/maven-assembly-plugin-do-not-trigger-search-of-default-assembly-descriptor) concerning a build failure with the maven-assembly-plugin, I could isolate the test-case that makes the issue appear.
Test Case :
- configure a project with a simple assembly, the property skipAssembly appears nowhere
- run the tasks "clean package assembly:single"
Current Result :
Build Failure
Expected Result :
Build Successfull as when running "clean package"
Workaround :
Add the property skipAssembly to true in the plugin configuration and add the property skipAssembly to false in the configuration of the execution
I have a project in my workspace that I can attach once the ticket created if I have the authorization to do so.
---
**Affects:** 2.5.3
**Attachments:**
- [build_failure_clean_package_assembly-single.txt](https://issues.apache.org/jira/secure/attachment/12727334/build_failure_clean_package_assembly-single.txt) (_2.84 kB_)
- [map-bug-0.1-SNAPSHOT-src.zip](https://issues.apache.org/jira/secure/attachment/12727335/map-bug-0.1-SNAPSHOT-src.zip) (_2.38 kB_)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the attached build_failure_clean_package_assembly-single.txt and map-bug-0.1-SNAPSHOT-src.zip, then reproduce the test case with "clean package assembly:single" on the Maven assembly plugin configuration described in the issue. Compare it with "clean package" and the stated skipAssembly workaround; done means the former completes successfully without requiring that workaround.
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