[
http://jira.codehaus.org/browse/MSHADE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116518
]
Dan Fabulich commented on MSHADE-7:
-----------------------------------
MSHADE-7 is a very different feature from shadedArtifactAttached.
MSHADE-7 suggests that the generated classes just get dumped in with the
regular classes, so I can just write my code directly against the shaded
packages.
In that case, there would be no separate shaded artifact; the main artifact
would be the only artifact, and no need to replace.
shadedArtifactAttached appends a new artifact with -shaded classifier, which
isn't as helpful because the non-shaded artifact is usually trash.
> 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
