Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.212.46 as permitted sender)
MIME-Version: 1.0
From: Kevin Sutter <kwsutter@gmail.com>
Date: Thu, 25 Oct 2012 08:15:01 -0500
Message-ID: 
 <CABH8erm=PQ=cwQMh83XEWSxaq0Y2v4OthOT9z+COMJ7-A+WKQA@mail.gmail.com>
Subject: [DISCUSS] Upgrade to use ASM 4 for our post-enhancement processing
To: users@openjpa.apache.org, dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=f46d042fdb3ed3d56804cce1fe9f

--f46d042fdb3ed3d56804cce1fe9f
Content-Type: text/plain; charset=ISO-8859-1

Hi,
Some of you may have noticed a recent JIRA I opened up:
https://issues.apache.org/jira/browse/OPENJPA-2283

I created this for upgrading our current usage of ASM 3.2 to ASM 4.0.
OpenJPA uses ASM for some post-enhancement processing to clean up the stack
map tables that are required for Java 7 validation.  Since ASM 4 has more
complete support for Java 7, I thought it would be an easy,
preventative-care type of move.

As my JIRA indicates, I have run into a couple of hiccups with this move
that I am still working through.

But, in general, does anybody have a concern with this upgrade?  I'm only
looking to do trunk at the moment.  But, if we continue to hit Java 7
validation errors in 2.2.x, then I might consider moving it back to 2.2.x
as well.

Thanks for any input,
Kevin

--f46d042fdb3ed3d56804cce1fe9f--