Attendees: 

Next meeting:

Agenda:

1. Updates for our October report to the board?
See mail from Bryan
AI: continue to work to optimize the TCK

2. JIRA JDO-843 "JDOQLTypedQuery: issue with candidate("this") method" 
https://issues.apache.org/jira/browse/JDO-843
- DN ticket #133 "JDOQLTypedQuery: wrong query result when replacing 
QFullTimeEmployee.candidate() by QFullTimeEmployee.candidate("this")"
https://github.com/datanucleus/datanucleus-api-jdo/issues/133
- New comment from Andy proposing changes in datanucleus-api-jdo source code: 
seems to work

Can we persuade DataNucleus to release a patched version as 5.2.10 so we do not 
have to stop support of JDK 8? 

We could then depend on 5.2.10 en route to 6.0.3. But there are five test case 
failures with 6.0.3 queries so more work there in any case. 

3. JIRA JDO-842 "Q class specification of candidate() method" 
https://issues.apache.org/jira/browse/JDO-842

In progress update to the specification:
The metamodel class has a public static method candidate(String name) that 
returns a new instance that can be used to generate query elements representing 
fields and properties.
The metamodel class has a public static method variable(String name, Expression 
exp) that returns a new instance that can be used to generate query elements 
that represent instances that can be navigated from candidate instances.
Footnote: The candidate and variable methods from JDOQLTypedQuery are 
deprecated because there is no user benefit. The javadoc calls out that the 
instances returned by these methods needs to be cast to the corresponding 
metadata class but this does not work with subclasses. Also, the sample queries 
will be updated to use the candidate("this") method.

4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812

5. sonarcloud issues

 * JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
 * JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https://issues.apache.org/jira/browse/JDO-823
 * Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo
 * Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo
 
 * Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo
 

6. Other issues

Action Items from weeks past:

[Sep 10 2024] AI Craig: write up proposed changes in a new branch and send for 
review.
[Sep 03 2024] AI Craig: create a new branch in specification to track spec 
changes
[Aug 27 2024] AI JDO-842: propose PR for specification (query chapter) and API 
(javadoc) and TCK (query tests). Use branches JDO-842 for this work. The 
specification has its own repository.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the parallel 
execution of tests Cast.java and SupportedOptionalMethods.java
[Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API 
disallows use with Android
[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores "https://issues.apache.org/jira/browse/JDO-651


Craig L Russell
c...@apache.org

Reply via email to