[
https://jira.codehaus.org/browse/MAPPASM-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295494#comment-295494
]
Karl Heinz Marbaise commented on MAPPASM-115:
---------------------------------------------
If i understand the
[maven-shade-documentation|http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html]
well it would a way to define the shaded artifact will be attached to the
orignal artifact with an classifier. Furthermore giving the shaded artifact
with classifier as dependency to appassembler-plugin should solve the problem
in my opinion?
> Appassembler doesn't notice shade
> ---------------------------------
>
> Key: MAPPASM-115
> URL: https://jira.codehaus.org/browse/MAPPASM-115
> Project: Mojo AppAssembler Plugin
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Benson Margulies
>
> If I use the maven-shade-plugin to roll my application up into one big jar,
> appassembler still grabs all the dependencies and builds a long classpath.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
