[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564658#comment-17564658 ] Thorbjørn Ravn Andersen commented on MASSEMBLY-925: --- [~cdomsch] As you are the reporter, you are the one who knows if the test case actually shows the issue you are reporting. If you would create a simple, artificial testcase showing the problem you see, I will give this a go. > 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 >Priority: Major > Labels: intern, up-for-grabs > > 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.20.10#820010)
[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107371#comment-17107371 ] Christian Domsch commented on MASSEMBLY-925: Ok, the case in question, as described, was an assembly that used dependencySets, where one dependency was of type zip and the zip in question was incidentally corrupted. I can try to create an artificial case, but you should be able to do that easily, as well. > 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)
[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106669#comment-17106669 ] Ian Lavallee commented on MASSEMBLY-925: 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)
[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006120#comment-17006120 ] Michael Osipov commented on MASSEMBLY-925: -- OK, thanks for the confirmation. > 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 >Priority: Major > > 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)
[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[ https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006055#comment-17006055 ] Christian Domsch commented on MASSEMBLY-925: Not, in this case it didn't help. This might also be due to the fact that -X caused such a tremendous amount of information that it overloaded everything. But regardless of that, I went into the -X logs and couldn't track down which dependency/artifact was causing the problem. > 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 >Priority: Major > > 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)
[jira] [Commented] (MASSEMBLY-925) Detailed error message on assembly failure
[
https://issues.apache.org/jira/browse/MASSEMBLY-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997637#comment-16997637
]
Michael Osipov commented on MASSEMBLY-925:
--
Did {{mvn -X}} not help?
> 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
>Priority: Major
>
> 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)
