Hi Greg, Grégory Joseph wrote:
> Hi, > > I have a project for which I'd like to create a shaded jar. > It has a bunch of dependencies in scope:provided, because they really > are, in the normal use-case of this artifact; it's meant to be > deployed as a plugin in another app, so, for example, myapp-api really > is "provided". > > The project also has an assembly, which depends on these deps to be > scope:provided (so they're not included in the assembly) > > If a webapp project is made and depends on this project, the > scope:provided also helps avoiding duplicated dependencies in some > cases. (I might have to double-check what I'm saying here ...) > > .. but yes, this project now also needs a standalone/executable jar; > some of the "provided" dependencies are needed at runtime for this. As > far as I can tell, the shade plugin currently does not propose any > solution for this. > > Is there any way this could be considered for the plugin ? Or am I > looking at it the wrong way ? Are there any alternatives ? I suppose I > could split my project and have 2 modules, one simply being the > standalone/shaded version of the other, but it seems overkill, since > they're really the same source. > > I've also looked at the assembly plugin, but as far as I can tell it > doesn't have a "minify" feature yet. (and we're talking 12mb vs 500k > when minified) > > I reported this as http://jira.codehaus.org/browse/MSHADE-89 > yesterday, before figuring it might be better discussed here > beforehand. > > Thanks for any tip or hint, Did you see this: http://maven.apache.org/plugins/maven-shade-plugin/shade- mojo.html#keepDependenciesWithProvidedScope - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
