[jira] [Commented] (JDO-822) Verify compatibility with JDK 21
[ https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780029#comment-17780029 ] Andy Jefferson commented on JDO-822: FYI, DataNucleus GitHub master (unreleased) has latest ASM, so should "support" Java 21. https://github.com/datanucleus/datanucleus-core/issues/495 > 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)
Re: [PR] JDO-822 - Add JDK 21 to matrix build (db-jdo)
tobous merged PR #84: URL: https://github.com/apache/db-jdo/pull/84 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Minutes: JDO TCK meeting Thursday October 26 1100 PDT 2000 CET
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Tuesday October 31 1200 PDT 2000 CET Agenda: 1. New PR #84 "JDO-822 - Add JDK 21 to matrix build" https://github.com/apache/db-jdo/pull/84 The TCK still builds to produce JDK 8. Andy says that DataNucleus is fine also. Good to merge. 2. JDO-830: "tck: Migrate JUnit tests to version 5 "https://issues.apache.org/jira/browse/JDO-830 Some progress migrating. Able to use more than one configuration. Previously generated a file tck-results with a summary of results. Needed to subclass the launcher to get results from each configuration. Still working. In JUnit5 there is no longer a difference between "error" and "failure". Both are failures. 3. JIRA JDO-831: "tck: improve tck tests for performance "https://issues.apache.org/jira/browse/JDO-831 Waiting on JDO-830. 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 21 " https://issues.apache.org/jira/browse/JDO-822 New comments 6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version " https://issues.apache.org/jira/browse/JDO-812 7. Other issues SonarCloud plans to require JDK17 instead of JDK11 for their runtime environment. This will affect all ASF projects using the tool. We expect ASF infra to handle the change. 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