You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Domsch (Jira)" <ji...@apache.org> on 2019/12/16 12:56:00 UTC
[jira] [Created] (MASSEMBLY-925) Detailed error message on assembly
failure
Christian Domsch created MASSEMBLY-925:
------------------------------------------
Summary: Detailed error message on assembly failure
Key: MASSEMBLY-925
URL: https://issues.apache.org/jira/browse/MASSEMBLY-925
Project: Maven Assembly Plugin
Issue Type: Improvement
Affects Versions: 3.2.0
Reporter: Christian Domsch
If the assembly fails during processing of its dependencySets/fileSets, it would be very convenient to get the current set/item it is trying to work on while it fails.
I just lost about a couple days worth of tracking down, why my assembly failed with the message: "Failed to create assembly: Error creating assembly archive base: archive is not a ZIP archive -> [Help 1]"
Long story short, in our package feed (we are building our software in Azure) one dependency that we used had a corrupt ZIP archive. Since this assembly is the final one we use to build our installers, it contains 50 dependencySets and some files and filesets. Which means, tracking down which of those was causing the issue while one build roughly takes 40mins is very time consuming.
In order to improve this, it would be very helpful, if in the event of an error, the plugin would tell you which module/dependency/file it actually failed on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)