2010/10/29 Grégory Joseph <greg....@gmail.com>: > 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, you have all the control on it. > On of the reasons my dependencies are in scope:provided, is because we > also build an assembly with the regular jar and a few text files. > Dependencies don't need to be shipped with this; we use a common > assembly descriptor where dependencies in scope:provided are excluded. Create another module for the assembly. This is a Maven best practice. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
