Btw, one of the ASM core committers is also an expert group member of the
JSR335 (java8/lambdas). So I suppose that if ASM isn't able to support
java8 bytecode yet, that should be fixable quite quickly.
2013/12/19 Stuart McCulloch
> On 19 Dec 2013, at 09:50, Kristian Rosenvold
> wrote:
>
> > T
On 19 Dec 2013, at 09:50, Kristian Rosenvold
wrote:
> That's me being imprecise based on something I picked off google; i changed
> the wiki.
>
> It would appear to me that the ASM based plugins are in for a decent bit of
> work (at least shade seems to be). Some of them are using fairly old
>
That's me being imprecise based on something I picked off google; i changed
the wiki.
It would appear to me that the ASM based plugins are in for a decent bit of
work (at least shade seems to be). Some of them are using fairly old
versions of asm too, and I considered
porting shade to 4.2 to minim
On 19 Dec 2013, at 08:08, Kristian Rosenvold
wrote:
> I figured we could use the wiki page to eventually document for end users
> which versions need to be used to solve known problems etc. While we're
> still fixing them and we're still ea it's probably a good place for just
> sharing knowledge
I figured we could use the wiki page to eventually document for end users
which versions need to be used to solve known problems etc. While we're
still fixing them and we're still ea it's probably a good place for just
sharing knowledge, since general stuff will tend to get hidden in jira.
jMNG-555
I just created
https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade to track
the status of java 8 migration "problems". This includes the bug number for
the bugs.sun.com bug report I just filed yesterday that makes verifier
break.
Kristian
