[jboss-jira] [JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588528#comment-13588528 ] 

Sanne Grinovero commented on WFLY-10520:
----------------------------------------

[~dmlloyd] suggested on chat to keep the transformer in a separate module "so we can deprecate & remove it later on"

That's an excellent point, and we also need a plan to make sure we can actually get rid of it - eventually.

For starters, could we make sure that each time the "transform" method is triggered an appropriate logging message is generated?

What else should we do to ensure people will swiftly move on - or at least have no way to not notice?

I'm understanding the plan is to have this transformer disabled by default, enabled by opt-in. Would it be sensible to have a default which would just check the bytecode for removed signatures and fail the deployment?





> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
>                 Key: WFLY-10520
>                 URL: https://issues.jboss.org/browse/WFLY-10520
>             Project: WildFly
>          Issue Type: Task
>          Components: JPA / Hibernate
>            Reporter: Gail Badner
>            Assignee: Scott Marlow
>             Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)