[jboss-jira] [JBoss JIRA] (WFLY-4036) update EclipseLink/OpenJPA test case to filter out javax.persistence classes

Scott Marlow (JIRA) issues at jboss.org
Fri Oct 31 10:21:35 EDT 2014


     [ https://issues.jboss.org/browse/WFLY-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow updated WFLY-4036:
-------------------------------
    Description: 
JBoss modules is improving the case when two modules have bi-directional dependencies (a depends on b and b depends on a).  Part of this is ensuring that module level classes are used over classes from dependencies (child first).  

This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA static module test).



  was:
WildFly-core upgrade is improving the case when two deployments have bi-directional dependencies (a depends on b and b depends on a).  Part of this is ensuring that application level classes are used over classes from dependencies.  

This introduces an issue for application that include api jars or other jars that previlously used to be overriden by dependency level classes.

This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA test).





> update EclipseLink/OpenJPA test case to filter out javax.persistence classes
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-4036
>                 URL: https://issues.jboss.org/browse/WFLY-4036
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 9.0.0.Beta1
>
>         Attachments: module.xml, module.xml, stacktrace.txt
>
>
> JBoss modules is improving the case when two modules have bi-directional dependencies (a depends on b and b depends on a).  Part of this is ensuring that module level classes are used over classes from dependencies (child first).  
> This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA static module test).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list