2010/10/29 Grégory Joseph :
> The only way I can get projectB's generated shaded jar to also include
> thirdParty is to redefine that dependency in projectB and change its
> scope.
I think this point is right and was implicit in the creation of this
special module for the shaded jar.
After all, yo
Hi again,
>> 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.
On 27 October 2010 19:33, Wayne Fay wrote:
> This is the correct approach (imo). Two artifacts, one for the
> pr
Hi Jörg,
> Did you see this:
> http://maven.apache.org/plugins/maven-shade-plugin/shade-
> mojo.html#keepDependenciesWithProvidedScope
I did, but it doesn't do what I need; my understanding is that it
changes the scope of the compile-scoped deps to :provided in the
shaded jar's pom.
Antonio, Way
2010/10/27 Grégory Joseph :
> .. 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 co
> 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 is the correct approach (imo). Two artifacts, one for the
provided artifact, another for the shaded artifact.
Wayne
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, my
