GitHub user rgilles opened a pull request:
https://github.com/apache/aries/pull/29
Use ASM5 Opcodes instead of the ASM4 and implement ASM 5 visitor api.
This solution fix issue on weaving code that use Java 8 specific language
features.
Without this fix you can get the following exception:
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)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rgilles/aries trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/aries/pull/29.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #29
----
commit 395c5bfad210efbbdfd3a8ea1c5ab204b59bd4fc
Author: rogilles <[email protected]>
Date: 2015-10-21T14:39:39Z
Use ASM5 Opcodes instead of the ASM4 and implement ASM visitor 5 api.
This solution fix issue on weaving code that use Java 8 specific language
features.
Without this fix you can get the following exception:
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)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
