Minutes: JDO TCK meeting Tuesday October 31 1200 PDT 2000 CET
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Tuesday November 7 1100 PST 2000 CET Agenda: 1. JDO-830: "tck: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-830 Currently using JUnit 5.9.3. But it no longer works subclassing the ConsoleLauncher because now with JUnit 5.10.0. the execute method no longer returns the number of tests, errors, failures, etc. So we will need to look into where the information is stored so we can maintain compatibility with how it works today. See the branch at: https://github.com/apache/db-jdo/tree/JDO-830 2. JIRA JDO-831: "tck: improve tck tests for performance" https://issues.apache.org/jira/browse/JDO-831 Waiting for JDO-830 3. 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=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo * Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo 4. JIRA JDO-822: "Verify compatibility with JDK 21" https://issues.apache.org/jira/browse/JDO-822 We compile with target JDK8. This now works with JDK21 as the compiler. This JIRA can be resolved. Will close when we release 3.2.2. Done. 5. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 6. Other issues Action Items from weeks past: [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 Recordshttps://openjdk.org/jeps/395 [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
[jira] [Updated] (JDO-822) Verify compatibility with JDK 21
[ https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen updated JDO-822: Fix Version/s: JDO 3.2.2 (was: JDO 3.3) > Verify compatibility with JDK 21 > > > Key: JDO-822 > URL: https://issues.apache.org/jira/browse/JDO-822 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Priority: Major > Fix For: JDO 3.2.2 > > > JDK 21 reached [General > Availability|https://openjdk.org/projects/jdk8/milestones#General_Availability] > on 19 September 2023, so we should go for JDK 21 instaed of JDK 20. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-822) Verify compatibility with JDK 21
[ https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen updated JDO-822: Fix Version/s: JDO 3.3 > Verify compatibility with JDK 21 > > > Key: JDO-822 > URL: https://issues.apache.org/jira/browse/JDO-822 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Priority: Major > Fix For: JDO 3.3 > > > JDK 21 reached [General > Availability|https://openjdk.org/projects/jdk8/milestones#General_Availability] > on 19 September 2023, so we should go for JDK 21 instaed of JDK 20. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-822) Verify compatibility with JDK 21
[ https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen resolved JDO-822. - Resolution: Fixed > Verify compatibility with JDK 21 > > > Key: JDO-822 > URL: https://issues.apache.org/jira/browse/JDO-822 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Priority: Major > > JDK 21 reached [General > Availability|https://openjdk.org/projects/jdk8/milestones#General_Availability] > on 19 September 2023, so we should go for JDK 21 instaed of JDK 20. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781491#comment-17781491 ] Michael Bouschen commented on JDO-830: -- First version of JUnit 5 migration: https://github.com/apache/db-jdo/tree/JDO-830 > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
