[
https://issues.apache.org/jira/browse/OPENJPA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793428#comment-13793428
]
Mark Struberg commented on OPENJPA-2171:
----------------------------------------
We can do this of course, and fill it with the java.version by default. But I'm
not quite sure what the benefit would be. For doing our release we will still
use java6 for some time. And for running all the build in our CI the single
property is fine enough. I have no objection to introduce it though - just like
to verify if it's really useful before we have another property to maintain ;)
> 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, kernel.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)
