ASM 4 is required if you want to generate correct .class files for Java 7 bytecode from memory.
This was one of the problems I encountered sometime ago with the maven-scr-plugin, it used ASM 3.x which generated invalid bind/unbind methods ( or more, methods that didn't pass JDK7's more stricter byte code verifier ). It's also NOT API compatible from memory - so its not just a version number bump in a pom. On 29/09/2012, at 8:10 AM, Daniel Kulp <[email protected]> wrote: > > I was doing some testing with the latest Karaf 2.3.0 snapshot and discovered > that it only includes the 3.3.1 version of ASM. However, the Aries proxy > stuff now requires 4.x. Is that dependency going to be updated? Should > we have both to not break existing things? > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
