openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2171) asm should be optional
Date Wed, 09 Oct 2013 22:12:42 GMT

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

ASF subversion and git services commented on OPENJPA-2171:
----------------------------------------------------------

Commit 1530808 from [~struberg] in branch 'openjpa/branches/2.3.x'
[ https://svn.apache.org/r1530808 ]

OPENJPA-2283 use xbean-asm4-shaded ASM version as the dynamic handling doesn't work out

This makes sure we always have a guaranteed ASM version 4 regardless what ASM a
user might add to the project. This also rolls back the dynamic ASM handling of
OPENJPA-2171.

> asm should be optional
> ----------------------
>
>                 Key: OPENJPA-2171
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2171
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Assignee: Mark Struberg
>              Labels: 2.3.0-candidate
>             Fix For: 2.3.0
>
>         Attachments: ASM.patch
>
>
> openjpa uses since some versions asm but in tomee for instance we use a shade (through
the xbean one org.apache.xbean:xbean-asm-shaded to avoid classloading/version issues with
webapps/applications.
> it can be nice if openjpa can provide us an issue to this because we really don't want
to provide asm in our binaries.
> solutions can be to use the xbean shade, give us an interface to implement or to try
several implementation (xbean shade, asm,...) by reflection



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message