You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2016/09/13 15:09:20 UTC

[jira] [Updated] (OPENJPA-2662) get rid of serp

     [ https://issues.apache.org/jira/browse/OPENJPA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg updated OPENJPA-2662:
-----------------------------------
    Attachment: OPENJPA-2662_1.patch

This patch moves  the PCEnhancer to be an abstract class and the old impl to PCEnhancerSerp.

My goal was to introduce a (halfway) clean API which you can access through OpenJPAConfiguration#getPCEnhancerInstance()

We are not yet fully there, but we can start pushing a 2nd implementation to satisfy this interface but with pure ASM code. That will be the next step...

> 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
>
>         Attachments: OPENJPA-2662_1.patch
>
>
> 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)