See https://github.com/benson-basis/github-release-note-maven-plugin. IntelliJ is sure that sisu-guava is in the class path. I am now trying reordering the pom to see if it works to put real Guava at the head of the line.
dependency:tree: org.apache.maven:maven-plugin-api:jar:3.0.5:provided [INFO] | +- org.apache.maven:maven-model:jar:3.0.5:provided [INFO] | +- org.apache.maven:maven-artifact:jar:3.0.5:provided [INFO] | \- org.sonatype.sisu:sisu-inject-plexus:jar:2.3.0:provided [INFO] | \- org.sonatype.sisu:sisu-inject-bean:jar:2.3.0:provided [INFO] | \- org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:provided [INFO] | \- org.sonatype.sisu:sisu-guava:jar:0.9.9:provided On Fri, Nov 7, 2014 at 12:08 PM, Benson Margulies <[email protected]> wrote: > Oh, I thought this was old hat. Stand by ... > > On Fri, Nov 7, 2014 at 12:06 PM, Stuart McCulloch <[email protected]> wrote: >> AFAIK none of the Guava packages are exposed from maven core, so I’d be >> interested to know more about where these types are leaking and how to >> recreate this. >> >> -- >> Cheers, Stuart >> >> >> On Friday, 7 November 2014 at 16:59, Benson Margulies wrote: >> >>> Is there any possible way of insulating 3.0.x pipelines from the old >>> version of Guava that leaks in with Sisu-guice? (Other than shading a >>> current version of guice and using it?) >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> (mailto:[email protected]) >>> For additional commands, e-mail: [email protected] >>> (mailto:[email protected]) >>> >>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
