[jboss-jira] [JBoss JIRA] (WFLY-459) javassist should be exported to JPA/Hibernate (native) applications

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-459:
-----------------------------------

renamed jira to reflect that it is fine for the JPA deployer to export the javassist dependency to applications.  Also, Hibernate native applications will get the javassist dependency via the org.hibernate module (now changed to export javassist).

> javassist should be exported to JPA/Hibernate (native) applications
> -------------------------------------------------------------------
>
>                 Key: WFLY-459
>                 URL: https://issues.jboss.org/browse/WFLY-459
>             Project: WildFly
>          Issue Type: Task
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 10.0.0.CR5
>
>
> Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do.  In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency.  
> # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate.
> # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer).
> # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)