[
http://jira.codehaus.org/browse/MSHADE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MSHADE-45.
-----------------------------------
Resolution: Incomplete
Assignee: Benjamin Bentmann
The plugin offers the means to exclude unwanted files (see [Selecting Contents
for Uber
JAR|http://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html])
and to deal with service factories (see [Resource
Transformers|http://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html]).
The manifest {{Class-Path}} is pointless for a self-contained JAR as produced
by the Shade Plugin. The plugin is already used suited to produce runnable JARs
so it's not clear what this issue is about.
> DefaultShader should include entire jar file and build MANIFEST.MF classpath
> ----------------------------------------------------------------------------
>
> Key: MSHADE-45
> URL: http://jira.codehaus.org/browse/MSHADE-45
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
> Reporter: warren crossing
> Assignee: Benjamin Bentmann
> Priority: Critical
>
> I'm trying to build a standalone jar file with all the dep inside. So I can
> run it with java -jar.
> But some are already signed, sealed and have files with the same names
> META-INF/ factory files etc. and the jar file will not run.
> Is this within the scope of DefaultShader or should I create a JarShader but
> then how to autowire with plexus?
--
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
