[
http://jira.codehaus.org/browse/MSHADE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190261#action_190261
]
Mark Struberg commented on MSHADE-60:
-------------------------------------
fixed in rev 812606
I didn't add the list of extensions, because they may be subject of change. But
we now skip
depending artifacts of type=pom.
I also added an integration test to make sure that the transitive dependencies
pulled in via this pom-dependency gets picked up into the shaded jar.
If one has a dependency which cannot be opened via JarFile we now will at least
throw a verbose Exception with stating the exact file which failed. The user
can then exclude
this artifact from shading.
> [PATCH] maven shade plugin fails if artifact dependencies contain artifacts
> that cannot be opened with JarFile class
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MSHADE-60
> URL: http://jira.codehaus.org/browse/MSHADE-60
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Brane F. Gracnar
> Fix For: 1.2.2
>
> Attachments: maven-shade-plugin-1.2.1.patch
>
>
> Maven Shade plugin fails to create an artifact if artifact dependecies
> include artifacts that cannot be opened with JarFile JVM class.
> This behaviour happens if someone puts something
> <dependencies>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
