shade via intermediate modules On 24 September 2012 14:36, Eric Czech <[email protected]> wrote:
> Thank you, that's exactly what I was looking for. > > Is there a way to shade versions of an artifact in a particular way? > For example, if projects A and B depend on Guava r09 and projects C > and D depend on Guava 13.0.1, how can I make sure that each is > referencing the correctly shaded version when they're built into a > jar? > > On Mon, Sep 24, 2012 at 8:55 AM, Stephen Connolly > <[email protected]> wrote: > > Maven shade plugin can relocate all the classes into a different package > > for you in minutes of config and seconds of build time > > > > On 24 September 2012 13:43, Eric Czech <[email protected]> wrote: > > > >> Hi everyone, > >> > >> I'm continually running into issues with Guava dependencies where the > >> version of Guava we use is inconsistent with the version used by some > >> other third-party library or several third-party artifacts referenced > >> in our projects use incompatible versions. > >> > >> I'm considering getting the source code for the version of Guava we > >> use and just building it into a new artifact with a slightly different > >> package namespace (all the packages would start with com.custom.google > >> or something like that). > >> > >> Is there a better way to go about this in general? > >> > >> Thanks in advance! > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
