Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday Nov 26 1100 PST 2000 CET Agenda: 1. New JIRA JDO-845 "Update JDO dependencies" https://issues.apache.org/jira/browse/JDO-845 PR #98 https://github.com/apache/db-jdo/pull/98 Infrequent failures on JDK 17 but this did not cause the failures. Need to discuss whether to upgrade references in the code from javax.persistence and javax.transaction packages to jakarta packages. This affects annotations and transactions. This does not affect javax.jdo naming. AI: file a new JIRA to discuss this change. Volunteer needed. The SBOM discussion prompted this proposal. Good to merge changes as is. 2. SBOM discussion see https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials The JDO API pom was updated to include the SBOM generation. Under target: generated files bom.json and bom.xml Warnings on generation can be ignored according to maven developers. In order to publish SBOM for current releases, some work is needed: AI: check out the current jdo-api; modify the jdo pom.xml to include the request to generate the SBOM files; notify security team that these files are available and ask for instructions on publishing them. Volunteer needed. 3. JIRA JDO-842 "Q class specification of candidate() method" https://issues.apache.org/jira/browse/JDO-842 Need to look at new test cases in query test package: 20, 21, 22, and 23 was renamed. 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: [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
