Matthias Stevens created MSHADE-181:
---------------------------------------
Summary: CLONE - Allow including dependencies of scope:provided
Key: MSHADE-181
URL: https://jira.codehaus.org/browse/MSHADE-181
Project: Maven Shade Plugin
Issue Type: Wish
Affects Versions: 1.4
Reporter: Matthias Stevens
Assignee: Benson Margulies
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's assembly 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.
.. 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 ? 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
