[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106669#comment-17106669 ]
Ian Lavallee edited comment on MASSEMBLY-925 at 5/14/20, 2:35 PM: ------------------------------------------------------------------ Are you able to provide a reproducible test case? If not, can you give more details on how the projects and dependencies are set up? Snippets from the POMs may be helpful. was (Author: ilavallee): Can you give more details on how the projects and dependencies are set up? Snippets from the POMs may be helpful. > 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 > Assignee: Elliotte Rusty Harold > Priority: Major > Labels: intern > > 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)