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] > >
