[
https://issues.apache.org/jira/browse/OPENJPA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786215#comment-13786215
]
Mark Struberg edited comment on OPENJPA-2283 at 10/4/13 3:13 PM:
-----------------------------------------------------------------
+1
but we should change the lookup order as we don't know whether the 'native'
ASM stuff is 'good enough' for us (means ASM3++).
As alternative, we might also think about forcing the dependency to xbean-asm4.
I would actually even prefer this to the other options. once there is a non
compat change in asm, the xbean team will shade to a different package again.
Thus xbean-asm4 can co-exist beside any other ASM version without interference.
was (Author: struberg):
+1. but we should change the lookup order as we don't know whether the 'native'
ASM stuff is 'good enough' for us (means ASM3++).
As alternative, we might also think about forcing the dependency to xbean-asm4.
I would actually even prefer this to the other options. once there is a non
compat change in asm, the xbean team will shade to a different package again.
Thus xbean-asm4 can co-exist beside any other ASM version without interference.
> Upgrade to ASM 4 dependency
> ---------------------------
>
> Key: OPENJPA-2283
> URL: https://issues.apache.org/jira/browse/OPENJPA-2283
> Project: OpenJPA
> Issue Type: New Feature
> Components: Enhance
> Affects Versions: 2.3.0
> Reporter: Kevin Sutter
> Fix For: 2.3.0
>
>
> OpenJPA currently has a dependency on ASM 3.2 for some post-enhancement
> processing to fix up the stack map tables (Java 7 requirement). The latest
> release of ASM is 4.1, which just came out last week. The immediate need is
> to move up to ASM 4.0. We can entertain 4.1 at a later date.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
