Classloader isolation is not specific to Guice. Something must be going on if
you get incompatible guava version when using maven 3.0+. This is why I
recommend setting up a standalone example to investigate what it is.
On October 3, 2014 4:57:57 PM EDT, Christofer Dutz
wrote:
>Hi Igor,
>
>wel
I've just fixed MCOMPILER-224, MCOMPILER-157, and (by extension)
MCOMPILER-159.
Are there any objections to me calling the vote to release 3.2 now? I
was hoping to test the waters before it involves backing out a tag to
call things back.
Thanks,
-john
--
John Casey
---
GitHub: https://git
Hi Igor,
well I currently don't have a small example ... Flexmojos as the Pluin is a
pretty large beast and Falcon isn't a trivial example.
But I have been investigating this problem a little more and eventually the
problems comes from how Flexmojos is built.
Currently the plugin is built using
What version of Maven do you use? Can you provide a small standalone
example that demonstrate the problem? Like a sample plugin with a
trivial demo project, for example.
Generally, each Maven plugin runs in its own classloader with only
subset of Maven core classes available to it. Guava is not p
Hi,
I'm currently working on a plugin for the Apache Flex compiler Falcon. This
uses Guava in a version above 15.
Now maven seems to come with a Guava version ... 0.9.9 for Maven 3.0.x,
something about 11 for 3.1 and above.
The problem is that from version 15 on there was an API change Falcon de
