openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2283) Upgrade to ASM 4 dependency
Date Fri, 04 Oct 2013 15:41:41 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786261#comment-13786261
] 

Mark Struberg commented on OPENJPA-2283:
----------------------------------------

to make this more clear: for now we let the reflection stuff as is, but we only change the
lookup order to check for xbean-asm4 first, then the rest.

{code}
tryClass("org.apache.xbean.asm4.");
tryClass("org.apache.xbean.asm.");
tryClass("org.objectweb.asm.");
tryClass("org.springframework.asm.");
{code}

The argument is that we know that xbean-asm4 is perfect, xbean-asm3 is still good enough,
but org.objectweb.asm could even be ASM-2 and older. So if anyone ships his webapp with ASM-2
as dependency, we still would take xbean-asm4 if available (e.g. in Geronimo or TomEE).

> 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)

Mime
View raw message