[jboss-jira] [JBoss JIRA] (WFLY-459) javassist should be exported to JPA/Hibernate applications
Scott Marlow (JIRA)
issues at jboss.org
Mon Dec 7 14:44:00 EST 2015
[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Marlow updated WFLY-459:
------------------------------
Summary: javassist should be exported to JPA/Hibernate applications (was: javassist should be exported to container managed JPA + Hibernate native applications)
> javassist should be exported to JPA/Hibernate 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)
More information about the jboss-jira
mailing list