[
https://issues.apache.org/jira/browse/OPENJPA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791818#comment-13791818
]
Mark Struberg commented on OPENJPA-2283:
----------------------------------------
Tell me where the difference is between having a direct dependency to a badly
maintained version of asm jars which are NOT binary compatible with each other
vs having an Apache internal xbean-asm4-shaded which we maintain over at the
Geronimo project?
There is a good reason why OpenWebBeans, OpenEJB, a few other Apache projects
plus Spring, etc dropped the direct ASM dependency already...
> 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
>
> Attachments: openjpa-2283.problem.patch
>
>
> 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)
