You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mauro Talevi (JIRA)" <ji...@codehaus.org> on 2007/12/11 10:25:57 UTC
[jira] Commented: (MSHADE-7) Shade should generate code, not
replace the jar
[ http://jira.codehaus.org/browse/MSHADE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116471 ]
Mauro Talevi commented on MSHADE-7:
-----------------------------------
Dan, have you tried configuring a shaded attached artifact - as in src/test/projects/shaded-attached-project?
That will create a new jar instead of replacing the original artifact.
> Shade should generate code, not replace the jar
> -----------------------------------------------
>
> Key: MSHADE-7
> URL: http://jira.codehaus.org/browse/MSHADE-7
> Project: Maven 2.x Shade Plugin
> Issue Type: Improvement
> Reporter: Dan Fabulich
>
> I frequently get errors replacing the output jar. (That's MSHADE-5.) It seems to me that it would be better if shade operated during the generate-sources phase, dropping the generated dependencies into a target/generated-sources directory.
> That way I could write my code directly against the shaded classes (rather than requiring shade do do the extra work of shading me as well).
> That would have the benefit of not needing to replace the artifact at package time, knocking out MSHADE-5, and making MSHADE-6 irrelevant as well.
--
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