[
https://jira.codehaus.org/browse/MSHADE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299843#comment-299843
]
Benson Margulies commented on MSHADE-75:
----------------------------------------
I claim that this case should not work, but it could 'not work' more politely.
What you've done is disrupt the production of the project's main artifact. By
adding a classifier to the default execution of the jar plugin, you've made the
jar plugin create an attached artifact *instead of* the main 'jar' artifact.
This leaves the project 'naked' and no longer producing a jar, and so shade is
flummoxed. Arguably, this case should produce a diagnostic like the diagnostic
for non-jar projects, and that's what I'm going to make it do. Then, I believe
that you could exclude the project's main artifact from shade and ask for the
classified one instead.
> Package maven multimodule project with shade plugin : error in opening zip on
> directory
> ---------------------------------------------------------------------------------------
>
> Key: MSHADE-75
> URL: https://jira.codehaus.org/browse/MSHADE-75
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.3.1
> Environment: Ubuntu 9.04 - Jaunty Jackalope -, Eclispse (Galileo),
> java 1.6.0_16
> Reporter: Yoann Yonnet
> Labels: moreinfo
> Attachments: patch-maven-shade-plugin.txt, pom.xml
>
>
> Hello,
> I make a maven aggregator project with two modules.
> The first module is a dependency of the second.
> The first module is build with the install goal.
> The second with the shade plugin during the package phase.
> The first module build runs successfully and install resulting jar file in
> the maven local repository.
> The second module build fails with this error :
> {noformat}[INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error creating shaded jar: error in opening zip file
> /home/yoann/workspace/maven.1265640716107/trunk/tcx-ws-client/module1/target/classes
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Fri Feb 12 10:39:29 CET 2010
> [INFO] Final Memory: 59M/583M
> [INFO]
> ------------------------------------------------------------------------{noformat}
> It's due to the shade plugin whose tries to reference first module classes
> from target/classes repository instead of the jar file previously build.
> Therefore, it seems that the shade plugin doesn't work with a maven
> multimodules project.
> I manage to build my maven aggregator project by applying the attached patch
> (patch-maven-shade-plugin.txt) on the class ShadeMojo.java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
