[
https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980682#action_12980682
]
Michael Bouschen commented on JDO-647:
--------------------------------------
The three errors are not related to the maven 2 update:
- Errors (1) and (2) are due to recent JDOQL changes with the return type of
AVG in queries (see JDO-643). These errors should go away as soon as we upgrade
to the DataNucleus version 2.2.2. Andys comment: DN 2.2.2 (not yet released,
but downloadable as a nightly build).
- Error (3) is the issue I mentioned in the email "Query test failure with
newer derby version". The generted SQL query compiles with derby 10.4.2.0, but
runs into the exception with newer derby versions 10.6.1.0 and 10.7.1.1. I do
not know how strict SQL defines the typing in equal comparisons: is is legal to
compare a boolean with an integer? So this might be a derby or a DataNuclues
issue.
> Run TCK using Maven2 for consistency
> ------------------------------------
>
> Key: JDO-647
> URL: https://issues.apache.org/jira/browse/JDO-647
> Project: JDO
> Issue Type: Improvement
> Components: tck
> Affects Versions: JDO 3
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1
>
> Attachments: api_pom.diff, exectck.zip, exectck.zip,
> JDO-647-pom-properties.zip, pom.xml, pom.xml
>
>
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to
> build/run the TCK using that too. It also means that the DataNucleus M1 repo
> (which only exists for use of this TCK) can be deleted. Please consider
> upgrading to Maven2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
