It's not only Serp, we also have cglib to let go. 3 different bytecode libs simply seem a bit much for a single project ;) But we need to do step after step...
LieGrue, strub > On Saturday, 3 September 2016, 16:27, Jody Grassel <[email protected]> wrote: > > I updated Serp a couple years ago to support Java 8's new Constant Pools > and instructions (that supports lambda expressions). There will likely be > Java 9 updates, but until the Java Virtual Machine Specification for v9 is > released there's nothing I can do. > > That said, I certainly would not shed a tear if the Serp dependency went > away. > > On Wed, Aug 31, 2016 at 2:00 PM, Mark Struberg (JIRA) <[email protected]> > wrote: > >> Mark Struberg created OPENJPA-2662: >> -------------------------------------- >> >> Summary: get rid of serp >> Key: OPENJPA-2662 >> URL: https://issues.apache.org/jira/browse/OPENJPA-2662 >> Project: OpenJPA >> Issue Type: Task >> Components: instrumentation >> Affects Versions: 3.0.0 >> Reporter: Mark Struberg >> Assignee: Mark Struberg >> Fix For: 3.0.0 >> >> >> We still use serp for parts of our byte code engineering. Serp is >> unmaintained and doesn't support java8++. Means we should get rid of > it. >> >> This is an aggregator ticket for all the subtasks >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >> >
