Hi,
I found a solution to the Java 25 problem.
We have to add the annotationProcessorPaths to the maven-compiler-plugin
configuration in the tck module.
I will create a JIRA and create a pull request. I hope the solution
works do for all the Java versions.
Regards Michael
Am 10.03.26 um 20:39 schrieb Craig Russell:
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday March 17 1200 PST 2000 CET
Agenda:
1. New GitHub Actions for Java 25 and DataNucleus 6.
see https://github.com/apache/db-jdo/pull/118
see https://github.com/tobous/db-jdo/actions/runs/22638982586/job/65609639183
see https://github.com/tobous/db-jdo/actions/runs/22638982586/job/65609639155
The Q classes are generated dynamically and the process fails on JDK25. May be
related to annotation processing changes:
https://medium.com/@roman.novosad87/migration-to-java-25-pitfalls-on-the-way-9b55ed036fee
Perhaps a change is needed in JDO Maven configurations (maven compiler plugin).
AI: Til ask DataNucleus user help page New Topic JDK25 support
2. Trusted Release project
Before we plan a new release we should take a look at the open SonarCloud
issues.
3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
4. JDO-847 "Create SBOM files" https://issues.apache.org/jira/browse/JDO-847
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:
[Jan 13 2026] AI Craig report trusted release issues to atr team.
[Aug 05 2025] AI everyone write to trusted release with errors in
https://release-test.apache.org/projects/db-jdo + AI everyone take a look and
tell the trusted release team what you find.
[Jul 01 2025] AI everyone take a look at the process for alpha testing. May
require a file in the dist directory to get started.
[Nov 12 2024] AI Michael see if it makes sense to add Map.contains(Entry e) to the JDO API. This
would be useful to have queries where e.g. the user is interested in finding all Employees where
the phone number is of key "home" and value "+16508617767".
[Nov 05 2024] AI Michael create a JIRA for containsEntry, include the current
test case and we can continue from here.
[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
[email protected]
