JDO TCK meeting Tuesday May 21 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday May 21 1100 PDT 2000 CEST 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


Unexpected query performance numbers in datanucleus log 
https://github.com/datanucleus/datanucleus-api-jdo/issues/130


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-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:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

Re: Minutes: JDO TCK meeting Tuesday May 14 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

just a small remark below ...


Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell

Next meeting: Tuesday May 21 1100 PDT 2000 CEST

Agenda:

1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835

Before executing a prepared statement, DataNucleus puts the statement into a 
cache keyed by thread id. In order to be canceled, the query must have been 
translated into a prepared statement and executed. This is the reason that 
cancel sometimes was not executed by DataNucleus. Michael made a change to the 
TCK to wait long enough and a change to DataNucleus to throw a DataNucleus 
exception if Derby does not support it.

AI Michael continue to make changes...


The statement above belongs to agenda item "2. JIRA JDO-836" below.

Regards Michael



2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836

Unexpected query performance numbers in datanucleus log 
https://github.com/datanucleus/datanucleus-api-jdo/issues/130

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-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:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the parallel 
execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday May 14 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday May 14 1100 PDT 2000 CEST 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


Unexpected query performance numbers in datanucleus log 
https://github.com/datanucleus/datanucleus-api-jdo/issues/130


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-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:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday May 7 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday May 7 1100 PDT 2000 CEST 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


Unexpected query performance numbers in datanucleus log 
https://github.com/datanucleus/datanucleus-api-jdo/issues/130


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-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:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday April 30 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday April 30 1100 PDT 2000 CEST 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


Unexpected query performance numbers in datanucleus log 
https://github.com/datanucleus/datanucleus-api-jdo/issues/130


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-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:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Updated] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-840:
-
Fix Version/s: (was: JDO 3.2.2)

> Fix changes links on JDO news site
> --
>
> Key: JDO-840
> URL: https://issues.apache.org/jira/browse/JDO-840
> Project: JDO
>  Issue Type: Improvement
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
>
> The current JDO site lists the JDO release on the start page. For each 
> release there is a link to the Jira version listing all the changes for the 
> particular release. For the releases older than JDO 3.2 you must be logged in 
> into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 
> this is not necessary.
>  * Change the link for the older release such that it is not necessary to be 
> logged into Jira to see the list.
>  * Releases older than 3.2 may not be downloaded anymore, so th etext "You 
> can download the release from ..." is misleading and shoudl be skipped.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen closed JDO-840.


> Fix changes links on JDO news site
> --
>
> Key: JDO-840
> URL: https://issues.apache.org/jira/browse/JDO-840
> Project: JDO
>  Issue Type: Improvement
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
>
> The current JDO site lists the JDO release on the start page. For each 
> release there is a link to the Jira version listing all the changes for the 
> particular release. For the releases older than JDO 3.2 you must be logged in 
> into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 
> this is not necessary.
>  * Change the link for the older release such that it is not necessary to be 
> logged into Jira to see the list.
>  * Releases older than 3.2 may not be downloaded anymore, so th etext "You 
> can download the release from ..." is misleading and shoudl be skipped.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday April 23 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday April 23 1100 PDT 2000 CEST 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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-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:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Resolved] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen resolved JDO-840.
--
Resolution: Fixed

> Fix changes links on JDO news site
> --
>
> Key: JDO-840
> URL: https://issues.apache.org/jira/browse/JDO-840
> Project: JDO
>  Issue Type: Improvement
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2
>
>
> The current JDO site lists the JDO release on the start page. For each 
> release there is a link to the Jira version listing all the changes for the 
> particular release. For the releases older than JDO 3.2 you must be logged in 
> into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 
> this is not necessary.
>  * Change the link for the older release such that it is not necessary to be 
> logged into Jira to see the list.
>  * Releases older than 3.2 may not be downloaded anymore, so th etext "You 
> can download the release from ..." is misleading and shoudl be skipped.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday April 16 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday April 16 1100 PDT 2000 CEST 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. db-jdo-site PR #52 "JDO-840: Fix changes links on JDO news site" 
https://github.com/apache/db-jdo-site/pull/52


2. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


3. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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=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 



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:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Created] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-840:


 Summary: Fix changes links on JDO news site
 Key: JDO-840
 URL: https://issues.apache.org/jira/browse/JDO-840
 Project: JDO
  Issue Type: Improvement
  Components: site and infrastructure
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


The current JDO site lists the JDO release on the start page. For each release 
there is a link to the Jira version listing all the changes for the particular 
release. For the releases older than JDO 3.2 you must be logged in into Jira to 
see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 this is not 
necessary.
 * Change the link for the older release such that it is not necessary to be 
logged into Jira to see the list.
 * Releases older than 3.2 may not be downloaded anymore, so th etext "You can 
download the release from ..." is misleading and shoudl be skipped.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen reassigned JDO-840:


Assignee: Michael Bouschen

> Fix changes links on JDO news site
> --
>
> Key: JDO-840
> URL: https://issues.apache.org/jira/browse/JDO-840
> Project: JDO
>  Issue Type: Improvement
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
>
> The current JDO site lists the JDO release on the start page. For each 
> release there is a link to the Jira version listing all the changes for the 
> particular release. For the releases older than JDO 3.2 you must be logged in 
> into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 
> this is not necessary.
>  * Change the link for the older release such that it is not necessary to be 
> logged into Jira to see the list.
>  * Releases older than 3.2 may not be downloaded anymore, so th etext "You 
> can download the release from ..." is misleading and shoudl be skipped.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-840) Fix changes links on JDO news site

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-840:
-
Fix Version/s: JDO 3.2.2

> Fix changes links on JDO news site
> --
>
> Key: JDO-840
> URL: https://issues.apache.org/jira/browse/JDO-840
> Project: JDO
>  Issue Type: Improvement
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2
>
>
> The current JDO site lists the JDO release on the start page. For each 
> release there is a link to the Jira version listing all the changes for the 
> particular release. For the releases older than JDO 3.2 you must be logged in 
> into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 
> this is not necessary.
>  * Change the link for the older release such that it is not necessary to be 
> logged into Jira to see the list.
>  * Releases older than 3.2 may not be downloaded anymore, so th etext "You 
> can download the release from ..." is misleading and shoudl be skipped.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday April 9 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday April 9 1100 PDT 2000 CEST 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. News for our April report to the board?

2. db-jdo-site PR #51 "Update downloads.adoc" 
https://github.com/apache/db-jdo-site/pull/51


3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


4. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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=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 



6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


7. Other issues

Action Items from weeks past:

[Mar 26 2024] AI Craig: merge PR #51  and remove the artifacts from dist.
[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday March 26 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday March 26 1200 PDT 2000 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. ASF - Infra newsletter for March, 2024: Policy change on use of 
GitHub Actions


2. New db-jdo-site PR #51 "Update downloads.adoc" 
https://github.com/apache/db-jdo-site/pull/51


3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


4. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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=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 



6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


7. Other issues

Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday March 19 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday March 19 1200 PDT 2000 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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-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:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday March 12 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday March 12 1100 PST 2000 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-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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-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:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday March 5 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday March 5 1100 PST 2000 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. Update GitHub Action versions

2. JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()" 
https://issues.apache.org/jira/browse/JDO-838

Do we need a spec update?

3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


4. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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=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 



6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


7. Other issues

Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Commented] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823326#comment-17823326
 ] 

Michael Bouschen commented on JDO-836:
--

New branch JDO-836:
 * Added cancel.conf configuration file
 * Added log Statements in QueryCancel TCK class
 * Disabled second test method in QueryCancel to avaoid parallel threads

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
 ] 

Michael Bouschen edited comment on JDO-836 at 2/27/24 7:20 PM:
---

I added some log statements to check that query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to tck/src/main/resources/conf {{and}} 
call mvn -Djdo.tck.cfglist=cancel.conf clean install in the tck subdirectory.


was (Author: mbo):
I added some log statements to check that query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to tck/src/main/resources/conf {{and}} 
call mvn -Djdo.tck.cfglist=cancel.conf clean install

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
 ] 

Michael Bouschen edited comment on JDO-836 at 2/27/24 7:19 PM:
---

I added some log statements to check that query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to tck/src/main/resources/conf {{and}} 
call mvn -Djdo.tck.cfglist=cancel.conf clean install


was (Author: mbo):
I added some lof statement to check that query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to tck/src/main/resources/conf {{and}} 
call mvn -Djdo.tck.cfglist=cancel.conf clean install

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
 ] 

Michael Bouschen edited comment on JDO-836 at 2/27/24 7:18 PM:
---

I added some lof statement to check that query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to tck/src/main/resources/conf {{and}} 
call mvn -Djdo.tck.cfglist=cancel.conf clean install


was (Author: mbo):
I added some lof statement to check thta query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to {{tck/src/main/resources/conf }}and call {{mvn 
-Djdo.tck.cfglist=cancel.conf clean install}}

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
 ] 

Michael Bouschen commented on JDO-836:
--

I added some lof statement to check thta query cancel is called after 
query.execute has been called:

22:14:11,040 (Query Executor) INFO  [org.apache.jdo.tck] - Start query execute  
               1708809251037
22:14:12,038 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - Start 
query cancel 1708809252038
22:14:12,039 (ForkJoinPool-1-worker-19) INFO  [org.apache.jdo.tck] - End query 
cancel   1708809252039
22:15:00,860 (Query Executor) INFO  [org.apache.jdo.tck] - End query execute    
                1708809300860
22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute took 
49823ms

You can use the attched configuration cancel.conf to run the QueryCancel TCK 
test. 
Copy the file cancel.conf to {{tck/src/main/resources/conf }}and call {{mvn 
-Djdo.tck.cfglist=cancel.conf clean install}}

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-836:
-
Attachment: cancel.conf

> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test 
> configuration so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday February 27 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday February 27 1100 PST 2000 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-838 "Clarify doc for query cancel()/cancelAll()" 
https://issues.apache.org/jira/browse/JDO-838
New PR #92 "Clarify javadoc of Query.cancel() and cancelAll()" 
https://github.com/apache/db-jdo/pull/92


2. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


3. JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


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=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 



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:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Resolved] (JDO-831) tck: improve tck tests for performance

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen resolved JDO-831.
--
Resolution: Fixed

TCK query test cases have been optimzed.

> tck: improve tck tests for performance
> --
>
> Key: JDO-831
> URL: https://issues.apache.org/jira/browse/JDO-831
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The performance of the tck test suite might be improved by using:
>  * multi-threading
>  * parallel execution of tests that do not change the database
>  * setup/teardown optimization for tests that do not change the database



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday February 20 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday February 20 1100 PST 2000 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. New JIRA JDO-839 "Lock at XML parser factory settings"
https://issues.apache.org/jira/browse/JDO-839
New PR #91 "Disable external entity processing"
https://github.com/apache/db-jdo/pull/91

2. JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()"
https://issues.apache.org/jira/browse/JDO-838
New PR #92 "Clarify javadoc of Query.cancel() and cancelAll()"
https://github.com/apache/db-jdo/pull/92

3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835

4 JIRA JDO-836 "TCK: QueryCancel Test class fails"
https://issues.apache.org/jira/browse/JDO-836

5. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
New PR #90 https://github.com/apache/db-jdo/pull/90

6. 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


7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812

8. Other issues

Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-0
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web: www.akquinet.de <http://www.akquinet.de/>

Geschäftsführung: Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[LinkedIn] <https://www.linkedin.com/company/akquinet/> [xing]
<https://www.xing.com/companies/akquinetag> [kununu]
<https://www.kununu.com/de/akquinet> [Instagram]
<https://www.instagram.com/akquinet_/>

smime.p7s
Description: S/MIME cryptographic signature

JDO TCK meeting Tuesday February 13 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday February 13 1100 PST 2000 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. GitHub security alert digest
-- derby
-- spring-beans update has been merged into main

2. New JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()" 
https://issues.apache.org/jira/browse/JDO-838


3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


4 JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


5. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


6. 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 



7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


8. Other issues

Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday January 23 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday January 23 1100 PST 2000 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. New JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835


2. New JIRA JDO-836 "TCK: QueryCancel Test class fails" 
https://issues.apache.org/jira/browse/JDO-836


3. New JIRA JDO-837 "TCK: add a JDO flag to enable/disable parallel 
execution" https://issues.apache.org/jira/browse/JDO-837


4. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


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=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 



6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


7. Other issues

Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

[jira] [Commented] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution

[Michael Bouschen (Jira)]

[ 
https://issues.apache.org/jira/browse/JDO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809131#comment-17809131
 ] 

Michael Bouschen commented on JDO-837:
--

The flag jdo.tck.parallel.execution ist added to the branch JDO-831

> TCK: add a JDO flag to enable/disable parallel execution
> 
>
> Key: JDO-837
> URL: https://issues.apache.org/jira/browse/JDO-837
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
>
> Add a flag to RunTCK to enable/disable parallel execution of the test methods 
> in TCK test classes:
> jdo.tck.parallel.execution=false|true default true
> The flag is used to set the flag junit.jupiter.execution.parallel.enabled



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-837:


 Summary: TCK: add a JDO flag to enable/disable parallel execution
 Key: JDO-837
 URL: https://issues.apache.org/jira/browse/JDO-837
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


Add a flag to RunTCK to enable/disable parallel execution of the test methods 
in TCK test classes:

jdo.tck.parallel.execution=false|true default true

The flag is used to set the flag junit.jupiter.execution.parallel.enabled



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen reassigned JDO-837:


Assignee: Michael Bouschen

> TCK: add a JDO flag to enable/disable parallel execution
> 
>
> Key: JDO-837
> URL: https://issues.apache.org/jira/browse/JDO-837
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
>
> Add a flag to RunTCK to enable/disable parallel execution of the test methods 
> in TCK test classes:
> jdo.tck.parallel.execution=false|true default true
> The flag is used to set the flag junit.jupiter.execution.parallel.enabled



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-836) TCK: QueryCancel Test class fails

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-836:


 Summary: TCK: QueryCancel Test class fails
 Key: JDO-836
 URL: https://issues.apache.org/jira/browse/JDO-836
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


The TCK test class QueryCancel fails. It is not part of any test configuration 
so it is never executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-835) TCK: Check ResultClassRequirementsMap when running multithreaded

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-835:


 Summary: TCK: Check ResultClassRequirementsMap when running 
multithreaded
 Key: JDO-835
 URL: https://issues.apache.org/jira/browse/JDO-835
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


The test cases of ResultClassRequirementsMap return wrong results when running 
multithreaded, see source code for details.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK meeting Tuesday January 16 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday January 16 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 



3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:

[Jan 09 2024] AI Michael Create a JIRA for the problem of 
ResultClassRequirementsMap test cases: if run multithreaded, returns 
wrong results but not consistently.
[Jan 09 2024] AI everyone: take a look into the 
ResultClassRequirementsMap issue.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday January 9 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday January 9 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 



3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[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

JDO TCK meeting Tuesday January 2 1100 PST 2000 CET

[Michael Bouschen]

Hi,

Happy New Year!

We will have our regular meeting Tuesday January 2 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 



3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. 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 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

JDO TCK meeting Tuesday December 19 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday December 19 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 



3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. 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 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

JDO TCK meeting Tuesday December 12 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday December 12 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 



3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:
[Dec 5 2023 ] AI Michael split SampleQueries into at least two classes.
[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

JDO TCK meeting Tuesday December 5 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday December 5 1100 PST 2000 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-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


2. 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 




3. JIRA JDO-822: "Verify compatibility with JDK 21" 
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:
[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

[jira] [Resolved] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen resolved JDO-830.
--
Resolution: Fixed

> 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.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)

JDO TCK meeting Tuesday November 28 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday November 28 1100 PST 2000 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-834 "Consider moving files instead of copying" 
https://issues.apache.org/jira/browse/JDO-834

Anything left?

2. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


3. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


4. JIRA JDO-834 "Consider moving files instead of copying" 
https://issues.apache.org/jira/browse/JDO-834


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=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 




6. JIRA JDO-822: "Verify compatibility with JDK 21" 
https://issues.apache.org/jira/browse/JDO-822


7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


8. 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

Re: Minutes: JDO TCK meeting Tuesday November 21 1100 PST 2000 CET

[Michael Bouschen]

Hi,


...

3. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830
PR #85 https://github.com/apache/db-jdo/pull/85

Still some issues with ConsoleLauncher writing to log files...
Good to merge. If still (color) issues with Console, another JIRA can be filed.


I found a way to disable the color in the junit result. The 
ConsoleLauncher has an option --disable-ansi-colors that does the job.


I checked in a change that makes use of option --disable-ansi-colors 
into the main branch. Please give it a try.


Regards Michael


Merged.

...

JDO TCK meeting Tuesday November 21 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday November 21 1100 PST 2000 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. New PR #86 "Export TCK logs in GitHub Action" 
https://github.com/apache/db-jdo/pull/86


2. New PR #87 "Bump org.apache.derby:derby from 10.14.2.0 to 10.17.1.0 
in /parent-pom" https://github.com/apache/db-jdo/pull/87

  automated security update

3. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830

PR #85 https://github.com/apache/db-jdo/pull/85

4. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


5. JIRA JDO-834 "Consider moving files instead of copying" 
https://issues.apache.org/jira/browse/JDO-834


6. 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 




7. JIRA JDO-822: "Verify compatibility with JDK 21" 
https://issues.apache.org/jira/browse/JDO-822


8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


9. 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

[jira] [Updated] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-830:
-
Fix Version/s: (was: JDO 3.2.2)

> 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.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)

JDO TCK meeting Tuesday November 14 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday November 14 1100 PST 2000 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. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830

PR #85 https://github.com/apache/db-jdo/pull/85

2. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


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


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

JDO TCK meeting Tuesday November 7 1100 PST 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday November 7 1100 PST 2000 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. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830

New PR #85 https://github.com/apache/db-jdo/pull/85

2. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


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

Andy updated his comment.

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

Re: Minutes: JDO TCK meeting Tuesday October 31 1200 PDT 2000 CET

[Michael Bouschen]

Hi Tilmann,

good idea!

I created PR #85 https://github.com/apache/db-jdo/pull/85

Regards
Michael


Hi Michael,

could you create PR?

That would simplify reviewing the code.

I think I can create a PR if you agree?

Best,
Til


On 02/11/2023 20:28, Michael Bouschen wrote:

Hi,
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

...


Update: JUnit provides an Interface TestExecutionListener and an
implementing class SummaryGeneratingListener that calculates the
number of tests, succeeds, failures etc.
I could add a subclass of SummaryGeneratingListener that prints the
test result in the file TCK-results.txt. This class is activated
through a service provider interface, so I added a file
org.junit.platform.launcher.TestExecutionListener under
META-INF/services including the name of the subclass
TCKSummaryGeneratingListener. I think this is the intended way to
handle the test execution result.

You find the update in the branch
https://github.com/apache/db-jdo/tree/JDO-830.

Regards
Michael

--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-0
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web: www.akquinet.de <http://www.akquinet.de/>

Geschäftsführung: Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[LinkedIn] <https://www.linkedin.com/company/akquinet/> [xing]
<https://www.xing.com/companies/akquinetag> [kununu]
<https://www.kununu.com/de/akquinet> [Instagram]
<https://www.instagram.com/akquinet_/>

Re: Minutes: JDO TCK meeting Tuesday October 31 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

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

...


Update: JUnit provides an Interface TestExecutionListener and an
implementing class SummaryGeneratingListener that calculates the number
of tests, succeeds, failures etc.
I could add a subclass of SummaryGeneratingListener that prints the test
result in the file TCK-results.txt. This class is activated through a
service provider interface, so I added a file
org.junit.platform.launcher.TestExecutionListener under
META-INF/services including the name of the subclass
TCKSummaryGeneratingListener. I think this is the intended way to handle
the test execution result.

You find the update in the branch
https://github.com/apache/db-jdo/tree/JDO-830.

Regards
Michael

--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-0
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web: www.akquinet.de <http://www.akquinet.de/>

Geschäftsführung: Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[LinkedIn] <https://www.linkedin.com/company/akquinet/> [xing]
<https://www.xing.com/companies/akquinetag> [kununu]
<https://www.kununu.com/de/akquinet> [Instagram]
<https://www.instagram.com/akquinet_/>

smime.p7s
Description: S/MIME cryptographic signature

[jira] [Commented] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

[ 
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)

JDO TCK meeting Tuesday October 31 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Tuesday October 31 1200 PDT 2000 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. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


2. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


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

New comments

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

JDO TCK meeting Thursday October 26 1100 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday October 26 1100 PDT 2000 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. New PR #84 "JDO-822 - Add JDK 21 to matrix build" 
https://github.com/apache/db-jdo/pull/84


2. JDO-830: "tck: Migrate JUnit tests to version 5 
"https://issues.apache.org/jira/browse/JDO-830


3. JIRA JDO-831: "tck: improve tck tests for performance 
"https://issues.apache.org/jira/browse/JDO-831


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=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 




5. JIRA JDO-822: "Verify compatibility with JDK 20 
"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

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

JDO TCK meeting Wednesday October 18 1200 PDT 2100 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Wednesday October 18 1200 PDT 2100 CEST 
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. JDO-830: "tck: Migrate JUnit tests to version 5 
"https://issues.apache.org/jira/browse/JDO-830


2. JIRA JDO-831: "tck: improve tck tests for performance 
"https://issues.apache.org/jira/browse/JDO-831


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 20 
"https://issues.apache.org/jira/browse/JDO-822

New comments

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

JDO TCK meeting Thursday October 12 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday October 12 1100 PDT 2000 CEST 
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. JDO-830: "tck: Migrate JUnit tests to version 5 
"https://issues.apache.org/jira/browse/JDO-830


2. JIRA JDO-831: "tck: improve tck tests for performance 
"https://issues.apache.org/jira/browse/JDO-831


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 20 
"https://issues.apache.org/jira/browse/JDO-822

New comments

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

[jira] [Updated] (JDO-822) Verify compatibility with JDK 21

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-822:
-
Description: 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.
Summary: Verify compatibility with JDK 21  (was: Verify compatibility 
with JDK 20)

> 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)

JDO TCK meeting Thursday October 5 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday October 5 1100 PDT 2000 CEST 
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. Updates for our October report to the board

2. JDO-830: "tck: Migrate JUnit tests to version 5 
"https://issues.apache.org/jira/browse/JDO-830


3. JIRA JDO-831: "tck: improve tck tests for performance 
"https://issues.apache.org/jira/browse/JDO-831


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=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 




5. JIRA JDO-822: "Verify compatibility with JDK 20 
"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

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

JDO TCK meeting Thursday September 21 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday September 21 1100 PDT 2000 
CEST 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. DOAP for JDO

2. JIRA JDO-833 "Use automated release infra for JDO releases" 
https://issues.apache.org/jira/browse/JDO-833


3. JDO-830: "tck: Migrate JUnit tests to version 
5"https://issues.apache.org/jira/browse/JDO-830


4. JIRA JDO-831: "tck: improve tck tests for 
performance"https://issues.apache.org/jira/browse/JDO-831


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=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 




6. JIRA JDO-822: "Verify compatibility with JDK 
20"https://issues.apache.org/jira/browse/JDO-822

New comments

7. JIRA JDO-812 "Move to JDK 11 as the lowest supported 
version"https://issues.apache.org/jira/browse/JDO-812


8. Other issues

Action Items from weeks past:
[Aug 31 2023] AI Craig: update the DOAP file to include the three 
subprojects.
[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

[jira] [Assigned] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen reassigned JDO-830:


Assignee: Michael Bouschen

> 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)

JDO TCK meeting Thursday September 14 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday September 14 1100 PDT 2000 
CEST 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. DOAP for JDO

2. JIRA JDO-833 "Use automated release infra for JDO releases" 
https://issues.apache.org/jira/browse/JDO-833


3. JDO-830: "tck: Migrate JUnit tests to version 
5"https://issues.apache.org/jira/browse/JDO-830


4. JIRA JDO-831: "tck: improve tck tests for 
performance"https://issues.apache.org/jira/browse/JDO-831


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=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 




6. JIRA JDO-822: "Verify compatibility with JDK 
20"https://issues.apache.org/jira/browse/JDO-822

New comments

7. JIRA JDO-812 "Move to JDK 11 as the lowest supported 
version"https://issues.apache.org/jira/browse/JDO-812


8. Other issues

Action Items from weeks past:
[Aug 31 2023] AI Craig: update the DOAP file to include the three 
subprojects.
[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

JDO TCK meeting Thursday September 7 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday September 7 1100 PDT 2000 CEST 
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. No DOAP for JDO

2. JIRA JDO-833 "Use automated release infra for JDO releases" 
https://issues.apache.org/jira/browse/JDO-833


3. JDO-830: "tck: Migrate JUnit tests to version 
5"https://issues.apache.org/jira/browse/JDO-830


4. JIRA JDO-831: "tck: improve tck tests for 
performance"https://issues.apache.org/jira/browse/JDO-831


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=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 




6. JIRA JDO-822: "Verify compatibility with JDK 
20"https://issues.apache.org/jira/browse/JDO-822

New comments

7. JIRA JDO-812 "Move to JDK 11 as the lowest supported 
version"https://issues.apache.org/jira/browse/JDO-812


8. Other issues

Action Items from weeks past:
[Aug 31 2023] AI Craig: update the DOAP file to include the three 
subprojects.
[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

[jira] [Updated] (JDO-833) Use automated release infra for JDO releases

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-833:
-
Description: 
Signing releases using automated release infra is a possibility for us to use 
for the next release. 

See https://infra.apache.org/release-signing.html#automated-release-signing

  was:Signing releases using automated release infra is a possibility for us to 
use for the next release. 


> Use automated release infra for JDO releases
> 
>
> Key: JDO-833
> URL: https://issues.apache.org/jira/browse/JDO-833
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> Signing releases using automated release infra is a possibility for us to use 
> for the next release. 
> See https://infra.apache.org/release-signing.html#automated-release-signing



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-833) Use automated release infra for JDO releases

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-833:


 Summary: Use automated release infra for JDO releases
 Key: JDO-833
 URL: https://issues.apache.org/jira/browse/JDO-833
 Project: JDO
  Issue Type: Task
  Components: site and infrastructure
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


Signing releases using automated release infra is a possibility for us to use 
for the next release. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-833) Use automated release infra for JDO releases

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-833:
-
Fix Version/s: JDO 3.2.2
   JDO 3.3

> Use automated release infra for JDO releases
> 
>
> Key: JDO-833
> URL: https://issues.apache.org/jira/browse/JDO-833
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> Signing releases using automated release infra is a possibility for us to use 
> for the next release. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: JDO TCK meeting Thursday August 31 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

I'm sorry, there is a family issue I have to take care and cannot join
today.

Regards Michael

Hi,

We will have our regular meeting Thursday August 31 1100 PDT 2000 CEST
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. New DB PMC member: Tobias Bouschen

2. No DOAP for JDO

3. Signing releases using automated release infra is a possibility for
us to use for the next release.
JIRA ticket?

4. JDO-830: "tck: Migrate JUnit tests to version
5"https://issues.apache.org/jira/browse/JDO-830

5. JIRA JDO-831: "tck: improve tck tests for
performance"https://issues.apache.org/jira/browse/JDO-831

6. 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



7. JIRA JDO-822: "Verify compatibility with JDK
20"https://issues.apache.org/jira/browse/JDO-822
New comments

8. JIRA JDO-812 "Move to JDK 11 as the lowest supported
version"https://issues.apache.org/jira/browse/JDO-812

9. 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




--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-33
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web: www.akquinet.de <http://www.akquinet.de/>

Geschäftsführung: Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook] <http://www.facebook.com/akquinet> [XING]
<https://www.xing.com/companies/akquinetag> [LinkedIn]
<https://www.linkedin.com/company/akquinet-ag> [Twitter]
<https://twitter.com/akquinet>

smime.p7s
Description: S/MIME cryptographic signature

JDO TCK meeting Thursday August 31 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday August 31 1100 PDT 2000 CEST 
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. New DB PMC member: Tobias Bouschen

2. No DOAP for JDO

3. Signing releases using automated release infra is a possibility for 
us to use for the next release.

JIRA ticket?

4. JDO-830: "tck: Migrate JUnit tests to version 
5"https://issues.apache.org/jira/browse/JDO-830


5. JIRA JDO-831: "tck: improve tck tests for 
performance"https://issues.apache.org/jira/browse/JDO-831


6. 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 




7. JIRA JDO-822: "Verify compatibility with JDK 
20"https://issues.apache.org/jira/browse/JDO-822

New comments

8. JIRA JDO-812 "Move to JDK 11 as the lowest supported 
version"https://issues.apache.org/jira/browse/JDO-812


9. 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

JDO TCK meeting Thursday August 24 1100 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday August 24 1100 PDT 2000 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. Signing releases using automated release infra is a possibility for us to 
use for the next release.

2. JDO-830: "tck: Migrate JUnit tests to version 
5"https://issues.apache.org/jira/browse/JDO-830

3. JIRA JDO-831: "tck: improve tck tests for 
performance"https://issues.apache.org/jira/browse/JDO-831

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=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


5. JIRA JDO-822: "Verify compatibility with JDK 
20"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

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

JDO TCK Conference Call Thursday July 20 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday July 20 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. Any way to reduce the number of messages sent to the dev list for 
changes in PRs?

See email discussion with cdutz

2. Signing releases using automated release infra

3. PR #83 "Clean up Enhancer.execute() " 
https://github.com/apache/db-jdo/pull/83


4. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


5. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


6. 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


7. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822

New comments

8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


9. 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 Records 
https://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

[jira] [Resolved] (JDO-832) Remove RunTCK option jdo.tck.skipJndi

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen resolved JDO-832.
--
Resolution: Fixed

> Remove RunTCK option jdo.tck.skipJndi
> -
>
> Key: JDO-832
> URL: https://issues.apache.org/jira/browse/JDO-832
> 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
>
>
> With JDO-827 the TCK comes with its own JNDI mock implementation.
> Without an JNDI implemention we needed to skip the JNDI TCK test cases when 
> running the tck from an automatic build. This is not necessary anymore, so we 
> do not need the  option jdo.tck.skipJndi anymore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK Conference Call Thursday July 13 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday July 13 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. Number of messages send to the dev list for changes in PRs

2. JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827

  Anything left?

3. JIRA JDO-832 "Remove RunTCK option jdo.tck.skipJndi" 
https://issues.apache.org/jira/browse/JDO-832

  PR #82 https://github.com/apache/db-jdo/pull/82

4. PR #83 "Clean up Enhancer.execute() " 
https://github.com/apache/db-jdo/pull/83


5. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


6. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


7. 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 



8. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822

New comments

9. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


10. Other issues

Action Items from weeks past:

[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://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

[jira] [Created] (JDO-832) Remove RunTCK option jdo.tck.skipJndi

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-832:


 Summary: Remove RunTCK option jdo.tck.skipJndi
 Key: JDO-832
 URL: https://issues.apache.org/jira/browse/JDO-832
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen
Assignee: Michael Bouschen
 Fix For: JDO 3.2.2, JDO 3.3


With JDO-827 the TCK comes with its own JNDI mock implementation.

Without an JNDI implemention we needed to skip the JNDI TCK test cases when 
running the tck from an automatic build. This is not necessary anymore, so we 
do not need the  option jdo.tck.skipJndi anymore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK Conference Call Thursday July 6 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday July 6 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827

  PR # 81 "JDO-827 Simplify JNDI " https://github.com/apache/db-jdo/pull/81

2. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


3. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


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=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 



5. JIRA JDO-822: "Verify compatibility with JDK 20" 
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

Action Items from weeks past:

[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://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

[jira] [Resolved] (JDO-829) api: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen resolved JDO-829.
--
Resolution: Fixed

> api: Migrate JUnit tests to version 5
> -
>
> Key: JDO-829
> URL: https://issues.apache.org/jira/browse/JDO-829
> Project: JDO
>  Issue Type: Task
>  Components: api
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The unit tests in the api 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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK Conference Call Thursday June 29 1200 PDT 2100 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday June 29 12:00 Pacific Daylight 
Time (PDT) 21:00 Central European Summer 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. JDO-829: "api: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-829

New PR #80 https://github.com/apache/db-jdo/pull/80

2. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


3. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


4. JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827


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=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 



6. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822

New comments

7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


8. Other issues

Action Items from weeks past:

[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395

[May 24 2023] AI Volunteers respond to JIRA JDO-827
[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

Re: Reschedule June 29 meeting?

[Michael Bouschen]

Hi,

2100 CET works for me, too.

Regards
Michael


2100 CET works for me.

Best,
Til

On 27/06/2023 18:11, Craig Russell wrote:

I may have a conflict on Thursday June 29 at 1100/2000.

Can we reschedule the call for one hour later? Thursday June 29 1200 
PDT 2100 CET.


Thanks,
Craig

Craig L Russell
c...@apache.org

JDO TCK Conference Call Thursday June 15 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday June 15 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. New JUnit JIRAs
    JDO-829: "api: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-829
    JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830


2. New JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831


3. JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827


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=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 



5. JIRA JDO-822: "Verify compatibility with JDK 20" 
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

Action Items from weeks past:

[June 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395

[May 24 2023] AI Volunteers respond to JIRA JDO-827
[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

[jira] [Updated] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-830:
-
Description: 
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]

  was:
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


> 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
>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)

[jira] [Updated] (JDO-831) tck: improve tck tests for performance

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-831:
-
Description: 
The performance of the tck test suite might be improved by using:
 * multi-threading
 * parallel execution of tests that do not change the database
 * setup/teardown optimization for tests that do not change the database

  was:
The performance of the tck test suite might be improved by using:
 * multi-threading
 * parallel execution of tests that do not change the database
 * setup/teardown optimization for tests that do not change the database

https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build


> tck: improve tck tests for performance
> --
>
> Key: JDO-831
> URL: https://issues.apache.org/jira/browse/JDO-831
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The performance of the tck test suite might be improved by using:
>  * multi-threading
>  * parallel execution of tests that do not change the database
>  * setup/teardown optimization for tests that do not change the database



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-831) tck: improve tck tests for performance

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-831:
-
Fix Version/s: JDO 3.2.2
   JDO 3.3

> tck: improve tck tests for performance
> --
>
> Key: JDO-831
> URL: https://issues.apache.org/jira/browse/JDO-831
> Project: JDO
>  Issue Type: Task
>  Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The performance of the tck test suite might be improved by using:
>  * multi-threading
>  * parallel execution of tests that do not change the database
>  * setup/teardown optimization for tests that do not change the database
> 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)

[jira] [Created] (JDO-831) tck: improve tck tests for performance

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-831:


 Summary: tck: improve tck tests for performance
 Key: JDO-831
 URL: https://issues.apache.org/jira/browse/JDO-831
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


The performance of the tck test suite might be improved by using:
 * multi-threading
 * parallel execution of tests that do not change the database
 * setup/teardown optimization for tests that do not change the database

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)

[jira] [Created] (JDO-830) tck: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-830:


 Summary: 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
 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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-829) api: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-829:
-
Description: 
The unit tests in the api 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

  was:The unit tests in the api subproject are using JUnit 4 and are written in 
a JUnit 3.8.1 style. The tests should be migrated to JUnit 5.


> api: Migrate JUnit tests to version 5
> -
>
> Key: JDO-829
> URL: https://issues.apache.org/jira/browse/JDO-829
> Project: JDO
>  Issue Type: Task
>  Components: api
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The unit tests in the api 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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (JDO-829) api: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen reassigned JDO-829:


Assignee: Michael Bouschen

> api: Migrate JUnit tests to version 5
> -
>
> Key: JDO-829
> URL: https://issues.apache.org/jira/browse/JDO-829
> Project: JDO
>  Issue Type: Task
>  Components: api
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>    Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The unit tests in the api subproject are using JUnit 4 and are written in a 
> JUnit 3.8.1 style. The tests should be migrated to JUnit 5.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-829) api: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-829:
-
Fix Version/s: JDO 3.2.2
   JDO 3.3

> api: Migrate JUnit tests to version 5
> -
>
> Key: JDO-829
> URL: https://issues.apache.org/jira/browse/JDO-829
> Project: JDO
>  Issue Type: Task
>  Components: api
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> The unit tests in the api subproject are using JUnit 4 and are written in a 
> JUnit 3.8.1 style. The tests should be migrated to JUnit 5.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-829) api: Migrate JUnit tests to version 5

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-829:


 Summary: api: Migrate JUnit tests to version 5
 Key: JDO-829
 URL: https://issues.apache.org/jira/browse/JDO-829
 Project: JDO
  Issue Type: Task
  Components: api
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


The unit tests in the api subproject are using JUnit 4 and are written in a 
JUnit 3.8.1 style. The tests should be migrated to JUnit 5.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-827) Consider (re-)moving JNDI support

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-827:
-
Description: 
The JDO API has two JNDI dependencies:
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context 
context)}} and 
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context context, 
ClassLoader loader)}}

The JNDI dependency complicates building and running the TCK (because of the 
non-free nature of the implementation). It is also the only part of the API 
that stops it being compatible with Android. The CI runs currently have all 
tests disabled that depend on JNDI (TBD, how does it compile without the 
classes???).

There are many options for simplifying this issue:
 * Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB, JMS.
 * Move the two methods into a separate JDOJNDIHelper. This would (probably) 
allow us to more easily exclude it from builds when desired, for example using 
Java 9 modules.
 * Provide a dummy implementation of the JNDI classes. This would allow 
compiling the API without problems (also on Android), but we would still need 
to exclude it from tests.
 * Switch to a free leightweight implementation, e.g. 
[https://github.com/h-thurow/Simple-JNDI] or 
https://github.com/dattack/standalone-jndi

  was:
The JDO API has two JNDI dependencies:
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context 
context)}} and 
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context context, 
ClassLoader loader)}}

The JNDI dependency complicates building and running the TCK (because of the 
non-free nature of the implementation). It is also the only part of the API 
that stops it being compatible with Android. The CI runs currently have all 
tests disabled that depend on JNDI (TBD, how does it compile without the 
classes???).


There are many options for simplifying this issue:
* Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB, JMS.
* Move the two methods into a separate JDOJNDIHelper. This would (probably) 
allow us to more easily exclude it from builds when desired, for example using 
Java 9 modules.
* Provide a dummy implementation of the JNDI classes. This would allow 
compiling the API without problems (also on Android), but we would still need 
to exclude it from tests.
* Switch to a free leightweight implementation, e.g. 
https://github.com/h-thurow/Simple-JNDI


> Consider (re-)moving JNDI support
> -
>
> Key: JDO-827
> URL: https://issues.apache.org/jira/browse/JDO-827
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.2, JDO 3.2.1
>Reporter: Tilmann Zäschke
>Priority: Major
>
> The JDO API has two JNDI dependencies:
> {{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context 
> context)}} and 
> {{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context 
> context, ClassLoader loader)}}
> The JNDI dependency complicates building and running the TCK (because of the 
> non-free nature of the implementation). It is also the only part of the API 
> that stops it being compatible with Android. The CI runs currently have all 
> tests disabled that depend on JNDI (TBD, how does it compile without the 
> classes???).
> There are many options for simplifying this issue:
>  * Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB, 
> JMS.
>  * Move the two methods into a separate JDOJNDIHelper. This would (probably) 
> allow us to more easily exclude it from builds when desired, for example 
> using Java 9 modules.
>  * Provide a dummy implementation of the JNDI classes. This would allow 
> compiling the API without problems (also on Android), but we would still need 
> to exclude it from tests.
>  * Switch to a free leightweight implementation, e.g. 
> [https://github.com/h-thurow/Simple-JNDI] or 
> https://github.com/dattack/standalone-jndi



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-828) Set up automated mail subjects for GitHub action responses

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-828:
-
Fix Version/s: JDO 3.2.2
   JDO 3.3

> Set up automated mail subjects for GitHub action responses
> --
>
> Key: JDO-828
> URL: https://issues.apache.org/jira/browse/JDO-828
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Reporter: Tobias Bouschen
>Assignee: Tobias Bouschen
>Priority: Minor
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> On the general Apache community page, a range of email subjects for automated 
> email created for different actions on GitHub have been suggested: 
> [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent]
> These settings should be applied to the JDO repositories.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-828) Set up automated mail subjects for GitHub action responses

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-828:
-
Component/s: site and infrastructure

> Set up automated mail subjects for GitHub action responses
> --
>
> Key: JDO-828
> URL: https://issues.apache.org/jira/browse/JDO-828
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Reporter: Tobias Bouschen
>Assignee: Tobias Bouschen
>Priority: Minor
>
> On the general Apache community page, a range of email subjects for automated 
> email created for different actions on GitHub have been suggested: 
> [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent]
> These settings should be applied to the JDO repositories.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

JDO TCK Conference Call Thursday June 8 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday June 8 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. New JIRA JDO-828 "Set up automated mail subjects for GitHub action 
responses" https://issues.apache.org/jira/browse/JDO-828
    New PR #78 "JDO-828 - Add setup for subjects for automated GitHub 
emails" https://github.com/apache/db-jdo/pull/78
    New PR #47 "JDO-828 - Add setup for subjects for automated GitHub 
emails" https://github.com/apache/db-jdo-site/pull/47


2. New PR #79 "Update GitHub action versions" 
https://github.com/apache/db-jdo/pull/79
    New PR #48 "Update GitHub action versions & replace deprecated 
commands " https://github.com/apache/db-jdo-site/pull/48



3. JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827


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=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 



5. JIRA JDO-822: "Verify compatibility with JDK 20" 
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

Action Items from weeks past:

[May 24 2023] AI Volunteers respond to JIRA JDO-827
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for 
testing.
[May 03 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade 
tests for multithreaded, first for upgrading JUnit; next for the API and 
next for the TCK.
[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

JDO TCK Conference Call Thursday June 1 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday June 1 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. New JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827


2. 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 



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:

[May 24 2023] AI Tobias: write a JDO JIRA and GitHub PR to see what 
happens with Mailing list configurations

[May 24 2023] AI Volunteers respond to JIRA JDO-827
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for 
testing.
[May 03 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade 
tests for multithreaded
[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

JDO TCK Conference Call Wednesday May 24 1200 PDT 2100 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Wednesday May 24 12:00 Pacific Daylight 
Time (PDT) 21:00 Central European Summer 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. Github settings in .asf.yaml (see email from Craig)

2. Mailing list configurations for discussion (see email from Craig)

3. New JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827


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=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 



5. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


6. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


7. Other issues

Action Items from weeks past:

[May 3 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade 
tests for multithreaded
[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

JDO TCK Conference Call Thursday May 11 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday May 11 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer 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. 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
PR #77 "JDO-823: Cognitive Complexity of methods should not be too high" 
https://github.com/apache/db-jdo/pull/77


  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 



2. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:

[May 3 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade 
tests for multithreaded
[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

JDO TCK Conference Call Wednesday May 3 1200 PDT 2100 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Wednesday May 3 12:00 Pacific Daylight 
Time (PDT) 21:00 Central European Summer 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. 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 




2. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:

[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

JDO TCK Conference Call Wednesday April 26 1200 PDT 2100 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Wednesday April 26 12:00 Pacific 
Daylight Time (PDT) 21:00 Central European Summer 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. 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
See PR #76 "JDO-823 - Make fields in JDOException final" 
https://github.com/apache/db-jdo/pull/76


  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


2. field/property converters

JIRA JDO-826 " @Convert Javadoc indicates support for 
@Target(ElementType.TYPE,...)" https://issues.apache.org/jira/browse/JDO-826


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:

[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

JDO TCK Conference Call Thursday April 20 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting TApril 20 11:00 Pacific Daylight Time 
(PDT) 20:00 Central European Summer 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. 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
See PR #75 "JDO-823 - Make JDOException immutable" 
https://github.com/apache/db-jdo/pull/75


  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


2. field/property converters

JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709
JIRA JDO-826 " @Convert Javadoc indicates support for 
@Target(ElementType.TYPE,...)" https://issues.apache.org/jira/browse/JDO-826
See PR #74 "JDO 826 - Fix @Convert javadoc for types" 
https://github.com/apache/db-jdo/pull/74


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:

[Apr 06 2023] AI Michael: In FetchPlan 186 getDetachmentRoots the return type is 
Collection, check changing it to Collection
[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

JDO TCK Conference Call Thursday April 6 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting TApril 6 11:00 Pacific Daylight Time 
(PDT) 20:00 Central European Summer 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. Updates for our quarterly report to the board?

2. 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

 * PR #72: JDO-823: Remove unused local variable
   "https://github.com/apache/db-jdo/pull/72;
 * 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


3. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


4. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


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:
[Mar 16 2023] AI Tobias JDOException.inPrintStackTrace is modified 
during the execution of the method: look into it.
[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: [db-jdo] 01/01: Update PropertyUtils.java

[Michael Bouschen]

Hi Craig,

you need to login into github in order to see the error messages Tobias
mentioned.

Checking the code formatting is a separate task from running the TCK
with Java 8, Java 11 and Java 17. The code formatting check task uses
Java 11 to run the code formatter. So this action never runs into the
error message saying you are using the wrong Java version.

Both profiles verify-format and format check the Java Version that is
use when running the profile and both fail when using Java 8. Actually
the message "Detected JDK Version: 1.8.0-331 is not in the allowed range
[11,)" comes from this check.

You got two different errors with github and locally: with github
checking the code format complaint about PropertyUtils.java and locally
you run into the issue that the code formatter does not work with Java 8.

Regards
Michael


Hi Craig,

I am not sure what you mean. When I look at the GitHub action, the formatting 
job fails as expected. It tells you which fails are formatted incorrectly. Here 
is the excerpt from the GitHub action logs for your PR:

Error:  Found 1 non-complying files, failing build
Error:  To fix formatting errors, run "mvn 
com.spotify.fmt:fmt-maven-plugin:format"
Error:  Non complying file: 
/home/runner/work/db-jdo/db-jdo/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java

Best regards,
Tobias


On 4 April 2023 16:02:13 CEST, Craig Russell  wrote:

Hi Michael,



On Apr 4, 2023, at 01:50, Michael Bouschen  wrote:

Hi Craig,

the maven plugin running the formatter requires Java 11 or higher:
   Detected JDK Version: 1.8.0-331 is not in the allowed range [11,)

So if you want to check the formatting or want to reformat the code you need to 
install Java 11.

I agree that this is the solution for running locally. But couldn't we 
configure mvn to *not* run this task if java 8 is detected, rather than run the 
tool and fail the build?

We discussed this (the formatter needs Javav 11 or higher) when I introduced 
the profile running the formatter and agrred this is not a problem.

The GitHub action still fails with no report of what the problem is. Is there 
any way except to run locally to figure out what its complaint is?

Thanks,
Craig

Regards
Michael


Hi Tobias,

Thanks for the hint. I changed the javadoc for the two methods and tried again.

The error message wasn't helpful but I ran mvn locally and now get:

org.apache.maven.enforcer.rule.api.EnforcerRuleException: Detected JDK Version: 
1.8.0-331 is not in the allowed range [11,).
 I have 1.8.361 installed according to the Java control panel (last updated 
today).
But my env has
JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home

I looked in my /Library/Java/JavaVirtualMachines and there is only the one VM 
installed there.

But that's just on my local machine. What is the problem with the GitHub runner?

I also found this from stackOverflow:

  clr% /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
 1.8.361.09 (x86_64) "Oracle Corporation" - "Java" /Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
 1.8.0_331 (x86_64) "Oracle Corporation" - "Java SE 8" 
/Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home

Any ideas?
Thanks,
Craig


On Apr 3, 2023, at 14:17, Tobias 
Bouschen  wrote:

Hi Craig,

the instructions on how to run the format jobs are given in the 
readme:https://github.com/apache/db-jdo#formatting-using-maven

GJF also formats javadoc. So my guess would be that the new javadoc is not formatted 
correctly. The issue is probably that the javadoc has a linebreak even though the 
character limit is not reached on the first line. If you want the second line to 
actually be printed as a second line in the javadoc, you have to add '' 
between the two lines. If you just add a blank line between the two javadoc lines, 
the formatter should do this for you.

Best regards,
Tobias

On 03/04/2023 22:25, Craig Russell wrote:

So the code format check failed. I cannot see anything wrong with the changes I 
made.

https://github.com/apache/db-jdo/actions/runs/4591159720/jobs/8107138939?pr=73

Error:  To fix formatting errors, run "mvn 
com.spotify.fmt:fmt-maven-plugin:format"
8275
  
<https://github.com/apache/db-jdo/actions/runs/4591159720/jobs/8107138939?pr=73#step:3:8276>Error:
  Non complying file: 
/home/runner/work/db-jdo/db-jdo/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
While I try to figure out how to run com.spotify.fmt could anyone just tell me 
what the problem is?

Thanks,
Craig


Begin forwarded message:

From:c...@apache.org
Subject: [db-jdo] 01/01: Update PropertyUtils.java
Date: April 2, 2023 at 15:28:40 PDT
To:"jdo-comm...@db.apache.org"  
Reply-To:jdo-dev@db.apache.org

This is an automated email from the ASF dual-hosted git repository.

clr pushed a comm

Re: [db-jdo] 01/01: Update PropertyUtils.java

[Michael Bouschen]

Hi Craig,

the maven plugin running the formatter requires Java 11 or higher:
  Detected JDK Version: 1.8.0-331 is not in the allowed range [11,)

So if you want to check the formatting or want to reformat the code you 
need to install Java 11.


We discussed this (the formatter needs Javav 11 or higher) when I 
introduced the profile running the formatter and agrred this is not a 
problem.


Regards
Michael


Hi Tobias,

Thanks for the hint. I changed the javadoc for the two methods and tried again.

The error message wasn't helpful but I ran mvn locally and now get:

org.apache.maven.enforcer.rule.api.EnforcerRuleException: Detected JDK Version: 
1.8.0-331 is not in the allowed range [11,).
 
I have 1.8.361 installed according to the Java control panel (last updated today).

But my env has
JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home

I looked in my /Library/Java/JavaVirtualMachines and there is only the one VM 
installed there.

But that's just on my local machine. What is the problem with the GitHub runner?

I also found this from stackOverflow:

  clr% /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
 1.8.361.09 (x86_64) "Oracle Corporation" - "Java" /Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
 1.8.0_331 (x86_64) "Oracle Corporation" - "Java SE 8" 
/Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home

Any ideas?
Thanks,
Craig


On Apr 3, 2023, at 14:17, Tobias Bouschen 
 wrote:

Hi Craig,

the instructions on how to run the format jobs are given in the readme: 
https://github.com/apache/db-jdo#formatting-using-maven

GJF also formats javadoc. So my guess would be that the new javadoc is not formatted 
correctly. The issue is probably that the javadoc has a linebreak even though the 
character limit is not reached on the first line. If you want the second line to 
actually be printed as a second line in the javadoc, you have to add '' 
between the two lines. If you just add a blank line between the two javadoc lines, 
the formatter should do this for you.

Best regards,
Tobias

On 03/04/2023 22:25, Craig Russell wrote:

So the code format check failed. I cannot see anything wrong with the changes I 
made.

https://github.com/apache/db-jdo/actions/runs/4591159720/jobs/8107138939?pr=73

Error:  To fix formatting errors, run "mvn 
com.spotify.fmt:fmt-maven-plugin:format"
8275
  
Error:
  Non complying file: 
/home/runner/work/db-jdo/db-jdo/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
While I try to figure out how to run com.spotify.fmt could anyone just tell me 
what the problem is?

Thanks,
Craig


Begin forwarded message:

From: c...@apache.org
Subject: [db-jdo] 01/01: Update PropertyUtils.java
Date: April 2, 2023 at 15:28:40 PDT
To: "jdo-comm...@db.apache.org" 
Reply-To: jdo-dev@db.apache.org

This is an automated email from the ASF dual-hosted git repository.

clr pushed a commit to branch clr-apache-array-copy
in repository https://gitbox.apache.org/repos/asf/db-jdo.git

commit 034060cb69ad0a10f9bdf5aca4d5a0c9c9c11e8c
Author: Craig L Russell 
AuthorDate: Sun Apr 2 15:28:34 2023 -0700

Update PropertyUtils.java

JDO-819 Fix code smells
Use "Arrays.copyOf", "Arrays.asList", "Collections.addAll" or 
"System.arraycopy" instead.
---
.../java/org/apache/jdo/exectck/PropertyUtils.java | 23 ++
1 file changed, 10 insertions(+), 13 deletions(-)

diff --git a/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java 
b/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
index 07473bce..eef6d73c 100644
--- a/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
+++ b/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
@@ -16,6 +16,7 @@ package org.apache.jdo.exectck;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
+import java.util.Arrays;
import java.util.Collection;
import java.util.List;
import java.util.Properties;
@@ -28,31 +29,27 @@ public class PropertyUtils {
   }

   /**
-   * Separates white space separated items from a String into Collection 
entries Used to collect
-   * command line argument lists into a Collection
+   * Separates white space separated items from a String into a Set
+   * Used to collect command line arguments
*
* @param names String of white space separated items
-   * @param list HashSet to contain String items
+   * @param set Set to contain String items
*/
-  public static void string2Set(String names, Collection list) {
+  public static void string2Set(String names, Collection set) {
 String[] items = names.split("[ \t\n]");
-for (String s : items) {
-  list.add(s);
-}
+set.addAll(Arrays.asList(items));
   }

   /**
-   * Separates white space separated items from a String into 

JDO TCK Conference Call Thursday March 30 1100 PDT 2000 CEST

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday March 30 11:00 Pacific 
Daylight Time (PDT) 20:00 Central European Summer 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

 * Loops should not contain more than a single "break" or "continue"
   statement:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS135=CODE_SMELL=db-jdo
 * Type parameter names should comply with naming convention:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS119=CODE_SMELL=db-jdo
 * Unused local variables should be removed:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS1481=CODE_SMELL=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:
[Mar 23 2023] AI Craig: In exectck PropertyUtils look at the method 
names and parameter names and javadoc for string2Set and string2List
[Mar 16 2023] AI Tobias JDOException.inPrintStackTrace is modified 
during the execution of the method: look into it.
[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

JDO TCK Conference Call Thursday March 23 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday March 23 12:00 Pacific 
Daylight Time (PDT) 20: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

 * Arrays should not be be copied using loops:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS3012=CODE_SMELL=db-jdo
 * Arrays should not be created for varargs parameters:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS3878=CODE_SMELL=db-jdo
 * Loops should not contain more than a single "break" or "continue"
   statement:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS135=CODE_SMELL=db-jdo
 * Mutable fields sould not be "public static":
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS2386=CODE_SMELL=db-jdo
 * Type parameter names should comply with naming convention:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS119=CODE_SMELL=db-jdo
 * Unused local variables should be removed:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS1481=CODE_SMELL=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:
[Mar 16 2023] AI Tobias JDOException.inPrintStackTrace is modified 
during the execution of the method: look into it.
[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

JDO TCK Conference Call Thursday March 16 1200 PDT 2000 CET

[Michael Bouschen]

Hi,

We will have our regular meeting Thursday March 16 12:00 Pacific 
Daylight Time (PDT) 20: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

 * Standard outputs shoudl not be used to log anything:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS106=MAJOR=CODE_SMELL=db-jdo
 * Unsed type parameters shoudl be removed:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS2326=MAJOR=CODE_SMELL=db-jdo
 * Exception classes should be immutable:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS1165=MINOR=CODE_SMELL=db-jdo
 * Arrays should be be copied using loops:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS3012=MINOR=CODE_SMELL=db-jdo
 * Arrays should not be created for varargs parameters:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS3878=MINOR=CODE_SMELL=db-jdo
 * Loops shoudl not contain more than a single "break" or "continue"
   statement:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS135=MINORtypes=CODE_SMELL=db-jdo
 * Mutable fields sould not be "public static":
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS2386=MINOR=CODE_SMELL=db-jdo
 * Type parameter names should comply with naming convention:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS119=MINOR=CODE_SMELL=db-jdo
 * Unused local variables should be removed:
   
https://sonarcloud.io/project/issues?resolved=false=java%3AS1481=MINOR=CODE_SMELL=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