openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OPENJPA-818) TCK module should use Geronimo JPA 2.0 EA jar
Date Fri, 05 Dec 2008 21:25:44 GMT

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

Michael Dick closed OPENJPA-818.
--------------------------------

    Resolution: Fixed
      Assignee: Michael Dick

I've changed the configuration to use Geronimo's API, but I haven't automatically excluded
the failing test. Individual users will have to do that manually.

> TCK module should use Geronimo JPA 2.0 EA jar
> ---------------------------------------------
>
>                 Key: OPENJPA-818
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-818
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 2.0.0
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The pom.xml file for the TCK module doesn't use the updated JPA 2.0 EA spec from Geronimo
so the TCK fails when we require one of the new classes (ie QueryBuilder).
> Switching the pom to use Geronimo's implementation resolves the missing classes issue,
but we fail the method signature test - this likely won't be updated until a new TCK is released.

> I'm not an expert but I believe the signature test (and only the signature test) may
be skipped by specifying -Djpatck.pkg.dir=com/sun/ts/tests/ejb30/ 
> as a command line argument when running the TCK through maven. Until we get an updated
TCK or someone with direct access to the TCK finds a better way to exclude the sig test I
suggest anyone interested in running the TCK use the argument above. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message