Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 29 1100 PDT 2000 CET
Agenda:
1. New JUnit JIRAs
JDO-829: "api: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-829
Some test classes that inherit from JUnit classes no longer need the superclass.
Some message print methods have different signatures.
Negative tests can be simplified with JUnit 5. No longe method.r need
try/catch; just need the assert call.
JDO-830: "tck: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-830
Many more tests compared to the api project. Will defer until api is done.
Whatabout exectck? Needs investigation.
2. New JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
This will need to wait until the other JIRAs (JDO-829 and JDO-830) are done.
Parameterized tests in JUnit 5 might be useful.
Test suites might make sense in light of configurations.
Suggestion from IntelliJ SonarLint plugin: make test classes and the test
methods package protected instead of public.
3. JIRA JDO-827 "Consider (re-)moving JNDI support"
https://issues.apache.org/jira/browse/JDO-827
4. 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
5. JIRA JDO-822: "Verify compatibility with JDK 20"
https://issues.apache.org/jira/browse/JDO-822
Recent statistics on JDK usage:
https://newrelic.com/resources/report/2022-state-of-java-ecosystem
Tobias added JDK20 to the set of JDKs to use for the tests. Results:
https://github.com/tobous/db-jdo/commit/a01db959898bfb0cd84b99f0510840c87704bba9
https://github.com/tobous/db-jdo/actions/runs/5170691272/jobs/9313757782
https://pipelines.actions.githubusercontent.com/serviceHosts/7b725ad1-bed5-4727-8ea3-c12c930e4e15/_apis/pipelines/1/runs/5/signedlogcontent/9?urlExpires=2023-06-15T18%3A39%3A40.4008195Z&urlSigningMethod=HMACV1&urlSignature=8zWoLaZw2erGFoYbhDA%2B9%2FCQYgrj95FpN780xuGXu7k%3D
6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
Still an objective once we have a major release planned.
7. Other issues
Action Items from weeks past:
[June 08 2023] AI All make a JIRA: JDO support for Java Records
https://openjdk.org/jeps/395
[May 24 2023] AI Volunteers respond to JIRA JDO-827
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for testing.
[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
