Minutes: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Thursday March 9 1100 PST 2000 CET Agenda: 1. 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 * Try-catch blocks should not be nested: https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo JDOHelper.getEnhancer method should be rewritten InstallSchema.loadSQLFileUsingJDBC method should be rewritten. Volunteer: Tilmann * Utility classes should not habe public constructors: https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo JDOHelper should not have a public constructor but is a breaking change, as JDOHelper is a public class. Resolution: "don't fix" until we have a "breaking change" release. LegacyJava should not have a public constructor. AI Michael change to a private constructor PropertyUtils should not have a public constructor. AI Michael change to a private constructor * Sections of code should not be commented out: https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo * Throwable and Error shoudl not be caught: https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo * Constructors of an abstract" class should not be declared "public": https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=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 2. JIRA JDO-709 "Standardize field/property converters" https://issues.apache.org/jira/browse/JDO-709 3. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. Other issues Action Items from weeks past: [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on JDO-709. [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using annotations and results of the test. [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
[GitHub] [db-jdo] sonarcloud[bot] commented on pull request #69: Remevod nested try-catch
sonarcloud[bot] commented on PR #69: URL: https://github.com/apache/db-jdo/pull/69#issuecomment-1450889770 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=db-jdo=69) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=db-jdo=69) No Coverage information [](https://sonarcloud.io/component_measures?id=db-jdo=69=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=db-jdo=69=new_duplicated_lines_density=list) -- 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
[GitHub] [db-jdo] sonarcloud[bot] commented on pull request #69: Remevod nested try-catch
sonarcloud[bot] commented on PR #69: URL: https://github.com/apache/db-jdo/pull/69#issuecomment-1450884853 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=db-jdo=69) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=db-jdo=69=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=db-jdo=69=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=db-jdo=69=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=db-jdo=69=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=db-jdo=69) No Coverage information [](https://sonarcloud.io/component_measures?id=db-jdo=69=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=db-jdo=69=new_duplicated_lines_density=list) -- 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
[GitHub] [db-jdo] tzaeschke opened a new pull request, #69: Remevod nested try-catch
tzaeschke opened a new pull request, #69: URL: https://github.com/apache/db-jdo/pull/69 Remove code smells of type: nested try-catch. See https://issues.apache.org/jira/browse/JDO-823. -- 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
Re: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET
well, dunno how that happened. the jdo meeting is in progress with just me > On Mar 1, 2023, at 12:07, Tilmann Zäschke wrote: > > I am getting "the host has another meeting in progress" ...? > > > On 01/03/2023 18:57, Tobias Bouschen wrote: >> Hi all, >> >> sorry for the short notice again, but I won't be able to attend today's >> conference call. I will see you all next week. >> >> Best regards, >> Tobias >> >> On 28/02/2023 20:58, Michael Bouschen wrote: >>> Hi, >>> >>> We will have our regular meeting Wednesday March 1 12:00 Pacific Standard >>> Time (PST) 21:00 Central European Time (CET) to discuss JDO TCK issues and >>> status. >>> >>> We use the following dial-in for audio and video: >>> https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 >>> >>> Agenda: >>> >>> 1. 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 >>> >>> * Try-catch blocks should not be nested: >>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo >>> >>> * Utility classes should not habe public constructors: >>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo >>> >>> * Sections of code should not be commented out: >>> https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo >>> >>> * Throwable and Error shoudl not be caught: >>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo >>> >>> * Constructors of an abstract" class should not be declared "public": >>> https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=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 >>> >>> >>> 2. JIRA JDO-709 "Standardize field/property converters" >>> https://issues.apache.org/jira/browse/JDO-709 >>> >>> 3. JIRA JDO-822: "Verify compatibility with JDK 20" >>> https://issues.apache.org/jira/browse/JDO-822 >>> >>> 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" >>> https://issues.apache.org/jira/browse/JDO-812 >>> >>> 5. Other issues >>> >>> Action Items from weeks past: >>> >>> [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on >>> JDO-709. >>> [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using >>> annotations and results of the test. >>> [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
Re: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET
I am getting "the host has another meeting in progress" ...? On 01/03/2023 18:57, Tobias Bouschen wrote: Hi all, sorry for the short notice again, but I won't be able to attend today's conference call. I will see you all next week. Best regards, Tobias On 28/02/2023 20:58, Michael Bouschen wrote: Hi, We will have our regular meeting Wednesday March 1 12:00 Pacific Standard Time (PST) 21:00 Central European Time (CET) to discuss JDO TCK issues and status. We use the following dial-in for audio and video: https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 Agenda: 1. 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 * Try-catch blocks should not be nested: https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo * Utility classes should not habe public constructors: https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo * Sections of code should not be commented out: https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo * Throwable and Error shoudl not be caught: https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo * Constructors of an abstract" class should not be declared "public": https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=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 2. JIRA JDO-709 "Standardize field/property converters" https://issues.apache.org/jira/browse/JDO-709 3. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. Other issues Action Items from weeks past: [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on JDO-709. [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using annotations and results of the test. [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
Re: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET
Hi all, sorry for the short notice again, but I won't be able to attend today's conference call. I will see you all next week. Best regards, Tobias On 28/02/2023 20:58, Michael Bouschen wrote: Hi, We will have our regular meeting Wednesday March 1 12:00 Pacific Standard Time (PST) 21:00 Central European Time (CET) to discuss JDO TCK issues and status. We use the following dial-in for audio and video: https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 Agenda: 1. 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 * Try-catch blocks should not be nested: https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo * Utility classes should not habe public constructors: https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo * Sections of code should not be commented out: https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo * Throwable and Error shoudl not be caught: https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo * Constructors of an abstract" class should not be declared "public": https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=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 2. JIRA JDO-709 "Standardize field/property converters" https://issues.apache.org/jira/browse/JDO-709 3. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. Other issues Action Items from weeks past: [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on JDO-709. [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using annotations and results of the test. [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
