aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-1437) Use ASM5 Opcodes instead of the ASM4 and implement ASM 5 visitor api.
Date Tue, 27 Oct 2015 11:22:27 GMT

     [ https://issues.apache.org/jira/browse/ARIES-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Bosschaert resolved ARIES-1437.
-------------------------------------
    Resolution: Fixed

I've applied the patch here: svn.apache.org/viewvc?view=revision&revision=1710765

Many thanks for your contribution, Romain!

> Use ASM5 Opcodes instead of the ASM4 and implement ASM 5 visitor api.
> ---------------------------------------------------------------------
>
>                 Key: ARIES-1437
>                 URL: https://issues.apache.org/jira/browse/ARIES-1437
>             Project: Aries
>          Issue Type: Bug
>          Components: SPI Fly
>    Affects Versions: spifly-1.0.2
>            Reporter: Romain Gilles
>            Assignee: David Bosschaert
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If weaving code use Java 8 specific language features you will end-up with this kind
of exception:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: INVOKESPECIAL/STATIC on interfaces require
ASM 5
> at org.objectweb.asm.MethodVisitor.visitMethodInsn(Unknown Source)
> at org.objectweb.asm.ClassReader.a(Unknown Source)
> at org.objectweb.asm.ClassReader.b(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61)
> {code}
> I provide a pull request in order to solve it:
> [https://github.com/apache/aries/pull/29]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message