> This problem is specific to maven-plugin-testing-harness. You can use
> any version of Guava at runtime, but test classpath is flat so you need
> to use single Guava version that is compatible with all components.
>
> Unfortunately, I don't know how to fix the problem, at least not until
> Maven
On 24 Jan 2014, at 23:49, Igor Fedorenko wrote:
> This problem is specific to maven-plugin-testing-harness. You can use
> any version of Guava at runtime, but test classpath is flat so you need
> to use single Guava version that is compatible with all components.
>
> Unfortunately, I don't know
This problem is specific to maven-plugin-testing-harness. You can use
any version of Guava at runtime, but test classpath is flat so you need
to use single Guava version that is compatible with all components.
Unfortunately, I don't know how to fix the problem, at least not until
Maven core is us
In the Android Maven Plugin we use the maven-plugin-api, which has a
transitive dependency to guava 10.0.1. Another dependency (android tools
common) pulls in 13.0.1 and things are fine so far.
However when I now upgrade to the latest version of the android tools I
get 15.0. Problem is that causes
