Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday Dec 17 1100 PST 2000 CET Agenda: 1. JIRA JDO-846 "Check upgrade references from javax to jakarta" https://issues.apache.org/jira/browse/JDO-846 2. JIRA JDO-847 "Create sbom files for JDO 3.2.1 release" https://issues.apache.org/jira/browse/JDO-847 PR #101: https://github.com/apache/db-jdo/pull/101 see https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials New branch JDO-847-2 now has the correct base 3.2.1 prior to the change to 3.2.2-SNAPSHOT. The maven calls will create the sboms in the target directory. cyclonedx target/bom.json and target/bom.jxml spdx: target/site/javax.jdo_jdo-api-3.2.1.spdx.json Interestingly the cyclonedx puts the sboms directly in target where the spdx puts them into target/site. There are some configurations that we need to explore. This experiment was successful. Next we need to update the main branch and update the documentation to enable the spdx and cyclonedx plugins. We will also need to discuss next steps with the security team to see how to publish the sboms consistent with other projects and consistent with the Tooling strategy. 3. JIRA JDO-842 "Q class specification of candidate() method" https://issues.apache.org/jira/browse/JDO-842 Minor correction: we should use "unconstrained" instead of "unbound" when discussing variables in queries. Unbound should refer to parameters that have no value. javax.jdo.query.JDOQL.UnconstrainedQueryVariables 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: [Dec 03 2024] AI Volunteer file a JIRA to replace SpringBeans with some other serializer. This may allow us to continue to support JDK8 with new version of serializer. [Nov 26 2024] AI Tilmann look into JDO-846. Also, what is the use for the Portable Remote Object interface (removed in JDK 11). [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 c...@apache.org
