from:"Craig Russell"

Minutes: JDO TCK meeting Tuesday May 7 1100 PDT 2000 CEST

2024-05-07 Thread Craig Russell

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

Next meeting: Tuesday May 14 1100 PDT 2000 CEST

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

Not response from DataNucleus. Andy, can you please take a look?

AI Michael take a look at the issue where DataNucleus swallows exceptions from 
statement.cancel(). We are running a version of DataNucleus (5) that supports 
JDK 8 (not the most recent). DataNucleus 6 requires JDK 11.

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

Minutes: JDO TCK meeting Tuesday April 30 1100 PDT 2000 CEST

2024-04-30 Thread Craig Russell

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

Next meeting: Tuesday May 7 1100 PDT 2000 CEST

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

Waiting for response from DataNucleus.

The other issue is DataNucleus will never throw an exception in response to 
query.cancel, even if the underlying datastore does not support it.

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

Re: JDO TCK meeting Tuesday April 23 1100 PDT 2000 CEST

2024-04-23 Thread Craig Russell

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

Next meeting: Tuesday April 30 1100 PDT 2000 CEST

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

Looking at the DataNucleus test case to see if there is any caching effect. 
There are wildly different results running Derby versus H2.
Trying to upload the test case to DataNucleus. Some permission issues to 
resolve...

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


Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday April 16 1100 PDT 2000 CEST

2024-04-16 Thread Craig Russell

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

Next meeting: Tuesday April 23 1100 PDT 2000 CEST

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

Good to go. Ok to merge.

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

Different behavior when running the test on Derby or H2.

AI Michael try to get DataNucleus to take a look at the strange behavior of the
special test. Once we have that sorted, we can modify the test to take another
flag for expected result of query cancel: either the thread executing the query
is canceled or the thread executing the cancel receives an exception.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday April 9 1100 PDT 2000 CEST

2024-04-09 Thread Craig Russell

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

Next meeting: Tuesday April 16 1100 PDT 2000 CEsT

Agenda:

1. News for our April report to the board?

No additional news. Thanks to Bryan for taking care of this.

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

Versions older than 3.2 point to a JIRA entry which is not publicly available.
AI Michael look at the difference between "changes" links for 3.1-rc1 and 3.2

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

Michael worked on a DataNucleus test case, running on Derby vs. H2.
He is preparing a test case to send to DataNucleus.

Step two is a test case that tests that DataNucleus reports an exception for
Derby query cancel.

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

Discussion for next meeting: Cyber Resilience Act will require more specific
actions for security. Topics:
SBOM (software bill of materials) and
SPDX (machine-readable license header) https://spdx.org/licenses/

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

Craig L Russell
c...@apache.org

Re: Derby behavior for Statement.cancel()

2024-03-26 Thread Craig Russell

Hi Rick,

Thanks so much for all of the work you did for us in this. Much more than I was 
expecting.

Best regards,
Craig

> On Mar 26, 2024, at 13:54, Rick Hillegas  wrote:
> 
> Hey Craig,
> 
> At the end of this message, I have attached a program which demonstrates the 
> behavior of Statement.cancel() in both the Derby embedded and network 
> drivers. As you can see from the following output, both drivers raise a 
> java.sql.SQLFeatureNotSupportedException exception. I ran the test on Open 
> JDK 22 using the latest Derby release (10.17.1.0):

Craig L Russell
c...@apache.org

Re: JDO TCK meeting Tuesday March 26 1200 PDT 2000 CET

2024-03-26 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Tuesday April 9 1100 PDT 2000 CEsT

Agenda:

1. ASF - Infra newsletter for March, 2024: Policy change on use of GitHub 
Actions for heavy users.

This does not affect the JDO project. 

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

The change will also affect the dist repo. 
AI Craig merge the request and remove the artifacts from dist. The artifacts 
will live on in the archives.

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

Still looking into DataNucleus test case to explain the difference in execution 
time.

Running a DataNucleus test case (using a different datastore H2):

21:13:25,490 (main) DEBUG [DataNucleus.Query] - JDOQL Query : Executing "SELECT 
max (this.x) FROM mydomain.model.Point WHERE this.x >= 0 && p2.x >= 0 VARIABLES 
mydomain.model.Point p2" ...
21:13:25,502 (main) DEBUG [DataNucleus.Datastore] - Using PreparedStatement 
"prep100: SELECT MAX(A0.X) FROM POINT A0 CROSS JOIN POINT VAR_P2 WHERE A0.X >= 
0 AND VAR_P2.X >= 0" for connection 
"org.datanucleus.store.rdbms.datasource.dbcp2.PoolingDataSource$PoolGuardConnectionWrapper@1c6ac73c"
21:13:25,502 (main) DEBUG [DataNucleus.Datastore.Native] - SELECT MAX(A0.X) 
FROM POINT A0 CROSS JOIN POINT VAR_P2 WHERE A0.X >= 0 AND VAR_P2.X >= 0
21:13:28,800 (main) DEBUG [DataNucleus.Datastore.Retrieve] - SQL Execution Time 
= 3298 ms
21:13:28,806 (main) DEBUG [DataNucleus.Query] - JDOQL Query : Execution Time = 
3316 ms

Still need to add a configuration option to the TCK to know what to expect from 
cancel().
We should also clarify the specification/javadoc regarding what the 
requirements are for query cancel.

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


Craig L Russell
c...@apache.org

Derby behavior for Statement.cancel()

2024-03-25 Thread Craig Russell

Hi,

You may notice that JDO is having a bit of a hard time trying to get our test 
for canceling a query to work. Our specification calls for throwing an 
exception if the JDBC driver does not support it. Our reference implementation 
is DataNucleus.

I'd like to verify that since you do not support Statement.cancel() that you 
throw an exception when you receive it. Hopefully, it's 
SQLFeatureNotSupportedException but for some reason we are not seeing it when 
we run DataNucleus and look for exceptions in the log.

I also tried to find the Derby implementation of cancel but could not (I got 
lost in the github repo). Could you give us a pointer to the code in the repo?

Many thanks,
Craig

Craig L Russell
c...@apache.org

Fwd: ASF - Infra newsletter for March, 2024

2024-03-23 Thread Craig Russell

Let's discuss this new Github policy on our normal schedule. Comments here, 
decisions here or at our regular meetings.

WDYT?

> Begin forwarded message:
> 
> From: Andrew Wetmore 
> Subject: ASF - Infra newsletter for March, 2024
> Date: March 23, 2024 at 05:59:32 PDT
> To: Users 
> 
> Welcome to Inside Infra for March, 2024.
> 
> Policy change on use of GitHub Actions
> 
> Due to misconfigurations in their builds, some projects have been using 
> unsupportable numbers of GitHub Actions. As part of fixing this situation, 
> Infra has added a 'resource use' section to the policy on GitHub Actions. 
> This section of the policy will come into effect on April 20, 2024:
> 
> All workflows MUST have a job concurrency level less than or equal to 20. 
> This means a workflow cannot have more than 20 jobs running at the same time 
> across all matrices.
> All workflows SHOULD have a job concurrency level less than or equal to 15. 
> Just because 20 is the max, doesn't mean you should strive for 20.
> The average number of minutes a project uses per calendar week MUST NOT 
> exceed the equivalent of 25 full-time runners (250,000 minutes, or 4,200 
> hours).
> The average number of minutes a project uses in any consecutive five-day 
> period MUST NOT exceed the equivalent of 30 full-time runners (216,000 
> minutes, or 3,600 hours).
> Projects whose builds consistently cross the maximum use limits will lose 
> their access to GitHub Actions until they fix their build configurations.
> The full policy is at  
> https://infra.apache.org/github-actions-policy.html
>  .
> 
> Roundtable summary
> 
> In the Roundtable of March 3, 2024, Clay Johnson of Gradle outlined the 
> testing features that come with Develocity, focussing on their use with 
> Gradle and Maven. For instance:
> 
> The build scan gives insights into what goes on in a build, and can help a 
> project quickly focus on tests that are failing or flaky, and address related 
> code issues.
> Predictive test selection can speed up certain types of builds by skipping 
> the tests that are not relevant to the build.
> A fuller summary of this discussion, and conversation about GitHub Runners 
> and other topics, is at  
> https://cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable+2024-03-06%2C+17%3A00+UTC
>  
> ,
>  and is available to ASF Members and Committers.
> 
> Note: There will be no April 2024 Roundtable. The series will resume in May.
> 
> The end of Apache Paste Bucket?
> 
> In 2013 Infra rolled out Apache Paste Bucket (http://paste.apache.org/ 
> ). In a blog entry at the time, we described it as 
> an "ASF-driven site for posting snippets, scripts, logging output, 
> configurations and much more and sharing them with the world."
> 
> The tool has seen some use over the past decade, but has had very little 
> traffic in the last couple of years. To keep Apache Paste Bucket available, 
> the code would require a significant upgrade. Unless we hear that the tool is 
> important to some part of the ASF community, we plan to shut down Apache 
> Paste in the near future.
> 
> ===
> 
> The next newsletter will appear toward the end of April, 2024.
> 
> -- 
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> Apache Software Foundation
> andr...@apache.org 
Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday March 19 1200 PDT 2000 CET

2024-03-19 Thread Craig Russell

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

Next meeting: Tuesday March 26 1200 PDT 2000 CET

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

Bouschen to Everyone (Mar 19, 2024, 12:15)
19:50:41,403 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Executing "SELECT avg (this.x + point2.y) FROM 
org.apache.jdo.tck.pc.mylib.PCPoint WHERE this.y >= 0 && point2.x >= 0 
VARIABLES PCPoint2 point2 import org.apache.jdo.tck.pc.mylib.PCPoint;import 
org.apache.jdo.tck.pc.mylib.PCPoint2;" ...
19:50:41,439 (Query Executor) DEBUG [DataNucleus.Datastore.Native] - SELECT 
AVG(CAST((A0.X + VAR_POINT2.Y) AS double)) FROM DATASTOREIDENTITY0.PCPOINT A0 
CROSS JOIN DATASTOREIDENTITY0.PCPOINT2 VAR_POINT2 WHERE A0.Y >= 0 AND 
VAR_POINT2.X >= 0

19:50:41,446 (Query Executor) DEBUG [DataNucleus.Datastore.Retrieve] - SQL 
Execution Time = 7 ms
19:50:53,947 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Execution Time = 12545 ms

19:45:33,619 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Executing "SELECT avg (this.x + point2.y) FROM 
org.apache.jdo.tck.pc.mylib.PCPoint WHERE this.y >= 0 && point2.x >= 0 && 
this.x >= (SELECT sum(p1.x + p1.y) FROM PCPoint p1 WHERE p1.x >= p1.y - 10) && 
point2.y >= (SELECT sum(p2.x + p2.y) FROM PCPoint p2 WHERE p2.x >= p2.y + 10) 
VARIABLES PCPoint2 point2 import org.apache.jdo.tck.pc.mylib.PCPoint;import 
org.apache.jdo.tck.pc.mylib.PCPoint2;" ...
19:45:33,671 (Query Executor) DEBUG [DataNucleus.Datastore.Native] - SELECT 
AVG(CAST((A0.X + VAR_POINT2.Y) AS double)) FROM DATASTOREIDENTITY0.PCPOINT A0 
CROSS JOIN DATASTOREIDENTITY0.PCPOINT2 VAR_POINT2 WHERE A0.Y >= 0 AND 
VAR_POINT2.X >= 0 AND A0.X >= (SELECT SUM((P1.X + P1.Y)) FROM 
DATASTOREIDENTITY0.PCPOINT P1 WHERE P1.X >= (P1.Y - 10)) AND VAR_POINT2.Y >= 
(SELECT SUM((P2.X + P2.Y)) FROM DATASTOREIDENTITY0.PCPOINT P2 WHERE P2.X >= 
(P2.Y + 10))

19:45:33,720 (Query Executor) DEBUG [DataNucleus.Datastore.Retrieve] - SQL 
Execution Time = 49 ms
19:45:33,726 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Execution Time = 107 ms

AI Michael create a new test case for DataNucleus to take a look. Also the 
wording of the TCK test case is misleading. And the catch clause in the cancel 
thread seems to be an incorrect copy/paste from the query execute thread.

a. Derby might ignore statement.cancel.
b. DataNucleus does not report exceptions but swallows the exception, but it 
still should log the exception in its internal log.
c. Why does it take 12 seconds for the implementation part of the query?
d. We need to look at adding a flag to the TCK configuration options 
DataStoreQueryCancelSupported[true/false]

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


Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday March 12 1100 PST 2000 CET

2024-03-12 Thread Craig Russell

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

Next meeting: Tuesday March 19 1200 PDT 2000 CET

Agenda:

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

No change.

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

Connection.createStatement creates a Statement
Statement.execute executes the SQL statement
Statement.cancel cancels the running statement
   SQLFeatureNotSupportedException - if the JDBC driver does not support this 
method
1. It appears that DataNucleus supports query cancellation but if the 
underlying datastore does not support it, no exception is thrown.
2. Big difference between SQL execution time and JDO Query execution time.
3. Try shorter lag between query execution and cancel.

20:52:20,569 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Executing "SELECT avg (this.x) FROM org.apache.jdo.tck.pc.mylib.PCPoint WHERE 
this.y >= 0 && point2.x >= 0 VARIABLES PCPoint2 point2 import 
org.apache.jdo.tck.pc.mylib.PCPoint;import 
org.apache.jdo.tck.pc.mylib.PCPoint2;" ...
20:52:20,603 (Query Executor) DEBUG [DataNucleus.Datastore.Retrieve] - SQL 
Execution Time = 8 ms
20:52:35,330 (Query Executor) DEBUG [DataNucleus.Query] - JDOQL Query : 
Execution Time = 14762 ms

AI Michael try to get more information from Andy on the DataNucleus 
implementation.

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


Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday March 5 1100 PST 2000 CET

2024-03-05 Thread Craig Russell

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

Next meeting: Tuesday March 12 1100 PST 2000 CET

Agenda:

1. Update GitHub Action versions

Tobias merged the change to 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?

Good as written. Once we figure out more details (see JDO-836) we can see if
updating the spec is needed.

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

Failure when running multithreaded. Keep JIRA open.

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

Michael updated the test case. FTR Derby does not support query cancel.
AI Michael update the test case to get more details on what if any errors are
returned by DataNucleus.
We need to decide what the behavior should be in the case where the PMF says
that cancel is supported but the JDO implementation or JDBC or database does
not support cancel. [This might be the reason the query cancel tests were never
activated...]

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:

Craig L Russell
c...@apache.org

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

2024-02-28 Thread Craig Russell

Hi Rick,

Thanks for the information. Saved me some time trying to sort this.

Warm regards,
Craig


> Begin forwarded message:
> 
> From: Rick Hillegas 
> Subject: Re: Fwd: [jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test 
> class fails
> Date: February 28, 2024 at 09:09:45 PST
> To: derby-...@db.apache.org, Craig Russell 
> 
> Hey Craig,
> 
> I don't know how DataNucleus tries to cancel a query.
> 
> jdbc.sql.Statement.cancel() is an optional method which some DBMSes implement 
> but Derby doesn't. The method raises a "Feature not supported" exception 
> according to https://db.apache.org/derby/docs/10.17/ref/rrefjdbc40794.html
> 
> 
> 
> On 2/27/24 5:27 PM, Craig Russell wrote:
>> Hi,
>> 
>> The JDO project is having some issues with a feature that was never formally 
>> tested: cancel query. It is intended to allow the JDO user to cancel a query 
>> from a different thread. It is an optional feature enabled by a user 
>> configuration flag.
>> 
>> The problem is that it does not seem to work. I've attached a log excerpt 
>> that shows that query starts in one thread, query cancel is called by the 
>> user to the DataNucleus implementation which then is supposed to call the 
>> Derby cancel query via JDBC.
>> 
>> Without diving into the details, can you confirm that the Derby JDBC 
>> implementation does implement query cancel without throwing an exception?
>> 
>> Thanks,
>> Craig
>> 
>>> Begin forwarded message:
>>> 
>>> From: "Michael Bouschen (Jira)" 
>>> Subject: [jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails
>>> Date: February 27, 2024 at 11:19:00 PST
>>> To: jdo-dev@db.apache.org
>>> Reply-To: jdo-dev@db.apache.org
>>> 
>>> 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 
>>> execute1708809300860
>>> 22:15:00,861 (Query Executor) INFO  [org.apache.jdo.tck] - query execute 
>>> took 49823ms
>>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday February 27 1100 PST 2000 CET

2024-02-27 Thread Craig Russell

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

Next meeting: Tuesday March 5 1100 PST 2000 CET

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

Good to go. Merged to main. The specification might use an update...
Volunteer for spec update?

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

It appears that the test case is written properly. 
Next question: does DataNucleus delegate to JDBC; 
and does Derby support query cancellation?
AI Craig ask on the derby dev list whether cancellation is supported.
AI Michael create a git branch with test case changes

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

- Question on where the web site sources are for ddlutils. Probably need to ask 
infra how to update contents for retired project.

- Random failures on JDK17
Caused by: java.lang.NullPointerException: Cannot invoke 
"org.datanucleus.state.ObjectProvider.preRollback(org.datanucleus.Transaction)" 
because "op" is null
org.datanucleus.ExecutionContextImpl.preRollback(ExecutionContextImpl.java:4546)
   [...]
 and JDK21
JUnit Jupiter:PMsCanSharePCClassesButNotPCInstances:testNonSharedPC()
Running tests for instancecallbacks.conf with applicationidentity:
  ** Tests found: 16, started: 16, succeeded: 15, failed: 1, skipped: 0, 
aborted: 0, time: 1.623 seconds


Action Items from weeks past:

[Jan 09 2024] AI everyone: take a look into the ResultClassRequirementsMap 
issue.
[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

Minutes: JDO TCK meeting Tuesday February 20 1100 PST 2000 CET

2024-02-20 Thread Craig Russell

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

Next meeting: Tuesday February 27 1100 PST 2000 CET
Agenda: 

1. New JIRA JDO-839 "Lock at XML parser factory settings" 
https://issues.apache.org/jira/browse/JDO-839 
<https://issues.apache.org/jira/browse/JDO-839>
New PR #91 "Disable external entity processing" 
https://github.com/apache/db-jdo/pull/91 
<https://github.com/apache/db-jdo/pull/91>
Looks good to merge. Resolve for 3.2.2

2. JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()" 
https://issues.apache.org/jira/browse/JDO-838
 <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 
<https://github.com/apache/db-jdo/pull/92>

The javadoc should indicate that only the thread executing the query should be 
canceled.

3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running 
multithreaded" https://issues.apache.org/jira/browse/JDO-835 
<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 
<https://issues.apache.org/jira/browse/JDO-836> 

Still working... The cancel method is designed to take several seconds and it 
appears not to be canceled.

Once the basic tests are working we can look at trying to cancel multiple 
executions of the method.
5. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831
 <https://issues.apache.org/jira/browse/JDO-831>New PR #90 
https://github.com/apache/db-jdo/pull/90 
<https://github.com/apache/db-jdo/pull/90>

OK to merge. Query tests have been improved. If additional improvements are 
warranted we can reopen the JIRA or make a new JIRA.

6. sonarcloud issues 

JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819 
<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 
<https://issues.apache.org/jira/browse/JDO-823> 

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo 
<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
 
<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
 
<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 
<https://issues.apache.org/jira/browse/JDO-812> 

8. Other issues 

Potential issue with documentation on the web site.

AI Tobias remove the old 2.0 API from the web site documentation but keep the 
packed API bundle. PR pending...

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 <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 <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 
<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 <mailto: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_/>
Craig L Russell
c...@apache.org

Attendees: JDO TCK meeting Tuesday February 13 1100 PST 2000 CET

2024-02-13 Thread Craig Russell

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

Next meeting: Tuesday February 20 1100 PST 2000 CET

Agenda:

1. GitHub security alert digest

Notifications will be sent based on settings.

-- derby
We would have to update our JDK dependency in order to handle this. But the
risk is tolerable due to our usage. Need to disable again.
Github security alert digest has details.

-- spring-beans update has been merged into main

-- JDOHelper
XML parsers should not be vulnerable to XXE attacks
https://github.com/apache/db-jdo/security/code-scanning/1

AI Tilmann look at possible solutions.

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

Should be linked with JDO-838 so we can clarify what the expected behavior is.

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

Michael looked at a few test cases which all consist of a single test method
that call different test methods.
Good to merge to main. If not merged, discuss at next meeting.

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:

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday January 23 1100 PST 2000 CET

2024-01-23 Thread Craig Russell

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

Next meeting: Tuesday February 13 1100 PST 2000 CET

Agenda:

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

May be a DataNucleus issue. Andy?

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

Test case fails: either the wrong exception or no exception for query cancel.
May be a DataNucleus issue. Andy?

AI Tilmann: raise a JIRA for better documentation of the cancel methods.
https://issues.apache.org/jira/browse/JDO-838

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

This change is only in the JDO-831 branch. It will be merged when 831 is merged.

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

Almost ready to merge into main.

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:

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday January 16 1100 PST 2000 CET

2024-01-16 Thread Craig Russell

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

Next meeting: Tuesday January 23 1100 PST 2000 CET

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

Some TCK tests needed updated due to the PCPoint equals implementation.
Query cancel was never executed in the past but they fail.

AI Michael file a JIRA for the failing test case.

Some tests still fail when run in parallel. Needs to be investigated.

AI Michael add a JDO flag to enable/disable parallel execution,.
junit.jupiter.execution.parallel.enabled configured via
jdo.tck.parallel.execution=false|true default true.

Maybe next look at the tests that take multiple seconds.

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

Tilmann is presenting at FOSDEM 2024
SCION network protocol
Sunday 12:00. main track

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday January 9 1100 PST 2000 CET

2024-01-09 Thread Craig Russell

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

Next meeting: January 16 1100 PST 2000 CET

Agenda:

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

Running tests for query-orig.conf with datastoreidentity:
  OK Tests found: 323, started: 323, succeeded: 323, failed: 0, skipped: 0, 
aborted: 0, time: 11.447 seconds
Running tests for query.conf with datastoreidentity:
  OK Tests found: 325, started: 325, succeeded: 325, failed: 0, skipped: 0, 
aborted: 0, time: 10.16 seconds
Running tests for query-orig.conf with applicationidentity:
  OK Tests found: 323, started: 323, succeeded: 323, failed: 0, skipped: 0, 
aborted: 0, time: 10.723 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 325, started: 325, succeeded: 325, failed: 0, skipped: 0, 
aborted: 0, time: 10.151 seconds

Modest improvement in performance by combining multiple classes into a single 
class with multiple test cases.

Almost done with the multithreaded upgrades.

Still one issue with running ResultClassRequirementsMap test class. If run 
multithreaded, returns wrong results but not consistently.

Ai everyone take a look.

https://github.com/apache/db-jdo/blob/JDO-831
tck/src/main/java/org/apache/jdo/tck/query/result/ResultClassRequirementsMap.java
line 85 describes the problem

This might be a DataNucleus bug.
AI Michael create a JIRA for this bug.

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


Craig L Russell
c...@apache.org

Re: Updates for our January report to the board, please?

2024-01-02 Thread Craig Russell

Hi Bryan,

Happy New Year. Here's some info from JDO:

Items for January board meeting:

The JDO project has a number of code improvements currently active. We are 
investigating use of automated release artifact signing to streamline release 
preparation. We have updated our automatic CI build to test with JDK 21 while 
maintaining compatibility with JDK 8 target (still seems to be the most popular 
deployment).

JDO is also working on improving performance of TCK tests by taking advantage 
of new features in JUnit 5 that allow for parallel execution of test cases 
where no changes to the datastore are made. This includes most query tests.

JDO also continues to work on code quality issues reported by SonarCloud.

Best,
Craig

> On Jan 1, 2024, at 15:50, Bryan Pendleton  wrote:
> 
> Hi all, it is time for our January report to the board.
> 
> Could you please send me any information about what the community has
> been working on over the last three months, so I can include them in
> the report?
> 
> thanks,
> 
> bryan

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday January 2 1100 PST 2000 CET

2024-01-02 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Tuesday January 9 1100 PST 2000 CET

Agenda:

Items for January board meeting:

The JDO project has a number of code improvements currently active. We are 
investigating use of automated release artifact signing to streamline release 
preparation. We have updated our automatic CI build to test with JDK 21 while 
maintaining compatibility with JDK 8 target (still seems to be the most popular 
deployment).

JDO is also working on improving performance of TCK tests by taking advantage 
of new features in JUnit 5 that allow for parallel execution of test cases 
where no changes to the datastore are made. This includes most query tests.

JDO also continues to work on code quality issues reported by SonarCloud.

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

Parallel execution is more work than expected. Currently the tests use a single 
setup and teardown per class but each test uses its own PersistenceManager.

Running tests for query.conf with datastoreidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 11.335 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 18.246 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 11.2 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 17.852 seconds

Parallelizing:

Running tests for query.conf with datastoreidentity:
  OK Tests found: 323, started: 323, succeeded: 323, failed: 0, skipped: 0, 
aborted: 0, time: 10.366 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 399, started: 399, succeeded: 399, failed: 0, skipped: 0, 
aborted: 0, time: 13.998 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 323, started: 323, succeeded: 323, failed: 0, skipped: 0, 
aborted: 0, time: 10.52 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 399, started: 399, succeeded: 399, failed: 0, skipped: 0, 
aborted: 0, time: 13.295 seconds

Next up: look at combining several test classes into a single class with 
multiple test methods. Some errors reported when running tests in parallel.
Cast.java line 96
SupportedOptionalMethods.java line 594

AI everyone: see if anyone can see a problem with the parallel execution of 
these tests.

logging set to debug:
NotEqual.java line 175 added some debug output
ReadSampleQueries.java line 162 added some debug output

Next up: combine multiple classes into one class in api.

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


Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday December 19 1100 PST 2000 CET

2023-12-19 Thread Craig Russell

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

Next meeting: Tuesday January 2 1100 PST 2000 CET

Agenda:

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

Separation of sample queries has been merged into the JDO-831 branch.
Read-only methods are annotated.

Results are encouraging for performance.

With setup and teardown once per method:

Running tests for query.conf with datastoreidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 23.993 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 23.342 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 24.619 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 27.754 seconds

With setup and teardown once per class:

Running tests for query.conf with datastoreidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 11.687 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 18.122 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 15.833 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 19.417 seconds

In the branch, the git tag pre-optimize disables the strategy for optimization.

AI everyone review the code in the branch. Take a look in particular to the 
annotations and setup and teardown methods. Also look at the class inheritance.

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


Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday December 12 1100 PST 2000 CET

2023-12-12 Thread Craig Russell

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

Next meeting: Tuesday December 19 1100 PST 2000 CET

Agenda:

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

Work is under way. First issue is initialization of methods and test classes:
setUp and tearDown.
New in JUnit beforeAll and afterAll.

https://www.baeldung.com/java-beforeall-afterall-non-static

SampleQueries has been split into separate classes: read-only and read-write.
SampleReadQueries and SampleModifyQueries.

AI Michael create a branch for JDO-831 and check in the sample query changes.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday December 5 1100 PST 2000 CET

2023-12-05 Thread Craig Russell

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

Next meeting: Tuesday December 12 1100 PST 2000 CET

Agenda:

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

First steps: see which tests are read-only. Look at class-based initialization
instead of method-based. JDOTest setup method calls localSetup.

Test class SampleQueries might be a good first case. Several dozen queries.
AI Michael split SampleQueries into at least two classes.
Query 20 seems to have some extraneous lines of code.
Three cases seem to be relevant:
Current serial execution
Shared PersistenceManager
Unique PersistenceManager per test method

https://junit.org/junit5/docs/current/user-guide/#writing-tests-parallel-execution
https://junit.org/junit5/docs/current/user-guide/#writing-tests-parallel-execution-synchronization
@Execution(CONCURRENT)
To be determined: can multiple test cases use the same PersistenceManager.

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

This is resolved now. A different issue is whether the TCK supports compiling
with target JDK not 8 and updating the Derby version.
AI volunteer create a JIRA to test target JDK~8 either as a one-off or as a new
setup option with a default JDK target.

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

5. Other issues

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday November 28 1100 PST 2000 CET

2023-11-28 Thread Craig Russell

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

Next meeting: Tuesday December 5 1100 PST 2000 CET

Agenda:

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

Ok to resolve. Close when we ship.

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

Possibly enable-ansi-colors as an option.
jdo.tck.testrunner.colors=enable or disable; default disable

Configuration list can comment out test classes using #

Ok to resolve once colors are implemented.

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

Next meeting we can start to discuss this.

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

See above.

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

Potential vulnerability in JDOHelper.
More investigation needed.

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

Craig L Russell
c...@apache.org

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

2023-11-21 Thread Craig Russell

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

Next meeting: Tuesday November 28 1100 PST 2000 CET

Agenda:

1. New PR #86 "Export TCK logs in GitHub Action"
https://github.com/apache/db-jdo/pull/86

Logs are uploaded with an expiration date + 2 weeks.
Good to merge.
Merged.

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
This is not needed by the TCK project. Close (will not accept this PR).

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

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

SonarCloud reported a potential security issue, which is visible only to team
members (not public):
https://github.com/apache/db-jdo/security/code-scanning/1

Action Items from weeks past:
[Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API
disallows use with Android
[Jun 08 2023] AI All make a JIRA: JDO support for Java
Recordshttps://openjdk.org/jeps/395
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for testing.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO
development and see if and how they want to be recognized on the JDO and DB web
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL
datastores "https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday November 14 1100 PST 2000 CET

2023-11-14 Thread Craig Russell

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

Next meeting: Tuesday November 21 1100 PST 2000 CET

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

Many constructive comments on the PR.
One issue is whether to copy log files to the logs directory and then reset the
current log. Perhaps a better way is to move the log file and create a new file
in its place.
AI Tilmann open a new JIRA for this, since it doesn't directly impact JUnit5
work.
https://issues.apache.org/jira/browse/JDO-834

Beside the log file issue, the PR is good for final review. JDO_Test is where
the major changes are.
AI everyone please take a look.

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

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Tuesday November 7 1100 PST 2000 CET

2023-11-07 Thread Craig Russell

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

Next meeting: Tuesday November 14 1100 PST 2000 CET

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

Several changes to the execute method might have been a separate PR but are
needed for the JUnit5 effort.

Failure on JDK11 on the GitHub machine.
AI Tobias try to configure the tck run to get more details on why the run fails
so we can debug it.

Optimizations on per-class setup will be done as a separate task. Some
initializations can be done once for multiple test methods instead of per test.

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

Craig L Russell
c...@apache.org

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

2023-10-31 Thread Craig Russell

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

Next meeting: Tuesday November 7 1100 PST 2000 CET

Agenda:

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

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

Waiting for JDO-830

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
We compile with target JDK8. This now works with JDK21 as the compiler.
This JIRA can be resolved. Will close when we release 3.2.2.
Done.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday October 26 1100 PDT 2000 CET

2023-10-26 Thread Craig Russell

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

Next meeting: Tuesday October 31 1200 PDT 2000 CET

Agenda:

1. New PR #84 "JDO-822 - Add JDK 21 to matrix build"
https://github.com/apache/db-jdo/pull/84
The TCK still builds to produce JDK 8. Andy says that DataNucleus is fine also.
Good to merge.

2. JDO-830: "tck: Migrate JUnit tests to version 5
"https://issues.apache.org/jira/browse/JDO-830
Some progress migrating. Able to use more than one configuration. Previously
generated a file tck-results with a summary of results. Needed to subclass the
launcher to get results from each configuration. Still working.
In JUnit5 there is no longer a difference between "error" and "failure". Both
are failures.

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

4. sonarcloud issues

JIRA JDO-819 "Code quality
analysis"https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Smells"https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link:https://sonarcloud.io/summary/overall?id=db-jdo

* Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false=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 21 "
https://issues.apache.org/jira/browse/JDO-822
New comments

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

7. Other issues

SonarCloud plans to require JDK17 instead of JDK11 for their runtime
environment. This will affect all ASF projects using the tool. We expect ASF
infra to handle the change.

Action Items from weeks past:
[Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API
disallows use with Android
[Jun 08 2023] AI All make a JIRA: JDO support for Java
Recordshttps://openjdk.org/jeps/395
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for testing.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO
development and see if and how they want to be recognized on the JDO and DB web
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL
datastores "https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Wednesday October 18 1200 PDT 2100 CET

2023-10-18 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Thursday October 26 1100 PDT 2000 CET

Agenda:

1. JDO-830: "tck: Migrate JUnit tests to version 5 "
https://issues.apache.org/jira/browse/JDO-830
The current way to get the output is way too complicated. Looking into
simplifying it.
Working on running more than one test.

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

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
Tobias has made a small change to build with 21. Seems to work ok.
AI Tobias: make a PR to build with 8, 11, 17, and 21.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday October 12 1100 PDT 2000 CEST

2023-10-12 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Wednesday October 18 1200 PDT 2100 CET

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

JUnit 5 has a few modules (not Java Modules) divided into parts. What we need
to change is how to run tests: ConsoleLauncher. Looks like this will work with
the existing .conf files with some changes in the runtck. JUnit3 has a naming
convention for test classes and test methods. JUnit4 and JUnit5 need an
annotation on the test classes to annotate every test method. Also setup and
teardown methods need annotations. JUnit 5 requires JDK8 or higher so no
worries there with our current support level.

Example of possible configuration usage: in the api project JDOHelperConfig
test line 291 has a parameterized configuration that runs three times based on
the settings.

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

It looks like JDK8 is still a very popular platform so there would have to be a
compelling reason to change.
JUnit 5 supports JDK8.
DataNucleus supports JDK8.

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

Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK meeting Thursday October 5 1100 PDT 2000 CEST

2023-10-05 Thread Craig Russell

Hi Bryan,

Here's a tad more detail on some of the topics.

JDO currently supports JDK 8, 11, and 17. We have tested JDK 20 in a branch and 
it looks good. Now that JDK 21 is GA, we will start CI testing using JDK 21 and 
look at testing with target JDK 11, 17, and 21 instead of target JDK 8.

As we look to upgrade from JUnit 3 we are now looking to improve the TCK 
configuration specifications.

Warm regards,
Craig

> On Oct 5, 2023, at 14:01, Bryan Pendleton  wrote:
> 
>> 1. Updates for our October report to the board
>> 
>> Items of note:
>> JDK21 is now an official release Generally Available as of September 19.
>> Tobias was elected to DB PMC.
>> JDO API module was upgraded to JUnit 5 from JUnit 3.
>> Still working on a release.
>> Looking at JDK 8, 11, 17, and now 21.
>> AI Craig send summary to DB PMC.
> 
> Thank you!
> 
> bryan

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday October 5 1100 PDT 2000 CEST

2023-10-05 Thread Craig Russell

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

Next meeting: Thursday October 12 11:00 PDT 20:00 CET

Agenda:

1. Updates for our October report to the board

Items of note:
JDK21 is now an official release Generally Available as of September 19.
Tobias was elected to DB PMC.
JDO API module was upgraded to JUnit 5 from JUnit 3.
Still working on a release.
Looking at JDK 8, 11, 17, and now 21.
AI Craig send summary to DB PMC.

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

Special classes were removed but need to integrate test runner. Looking at
improving the test configuration files.

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
We should upgrade the JIRA to JDK 21 since JDK 20 is no longer relevant.
AI Michael update the JIRA. Done.

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

7. Other issues

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday September 21 1100 PDT 2000 CEST

2023-09-21 Thread Craig Russell

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

Next meeting: Thursday October 5 1100 PDT 2000 CET

Agenda:

1. DOAP for JDO

The only possible issue is the name of the listing db-_JDO. Volunteer to "fix"
this? If not, drop from future agenda.

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

We will take this up when we prepare the next release.

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

First step to analyze: reduce TCK to a single test case. Refer to .jdo files in
metadata.
TestRunner and ResultPrinter classes not supported any more with JUnit 5, only
with the JUnit5 vintage that we currently use.

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

Should update this item to JDK 21 since 21 will be a LTS release.

7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
Also, JDK 11 (LTS) becomes EOL shortly.
Users are still running JDK 8 and JDK 11 "in production":
https://www.jetbrains.com/lp/devecosystem-2021/java/
https://www.jetbrains.com/lp/devecosystem-2022/java/

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday September 14 1100 PDT 2000 CEST

2023-09-14 Thread Craig Russell

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

Next meeting: Thursday September 21 11:00 PDT 20:00 CET

Agenda:

1. DOAP for JDO
https://projects.apache.org/doapfaq.html
The DOAP file was created from the template:
https://projects.apache.org/create.html
The DOAP file was merged to main:
https://github.com/apache/db-jdo-site/blob/main/doap__JDO.rdf
The index was updated:
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/committees.xml
The result is published under the projects site:
https://projects.apache.org/project.html?db-_jdo

Patches welcome.

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


Craig L Russell
c...@apache.org

Re: DOAP for JDO

2023-09-07 Thread Craig Russell

Hi Sebb,

I saw several references in the projects.xml file to git files, but none that 
are in the form https://github.com/apache/db-jdo-site/blob/main/doap.rdf

Which format would you suggest to use?
https://gitbox.apache.org/repos/asf?p=polygene-java.git;f=doap.rdf;a=blob_plain;hb=refs/heads/develop

Seems to be the most common. 

Please confirm that is what you recommend.

Thanks,
Craig

> On Sep 6, 2023, at 15:37, sebb  wrote:
> 
> On Wed, 6 Sept 2023 at 22:03, Craig Russell  wrote:
>> 
>> Hi Sebb,
>> 
>> I've created a DOAP for the JDO project but I'm having some trouble putting 
>> it into the proper place. My svn is a bit rusty and I'm not even sure I'm 
>> trying to put it where it belongs.
>> 
>> Could you help? I think it's ready to go into 
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/committers
>>  but I'm not sure.
> 
> The DOAP is normally stored in one of the repos for the relevant project.
> 
> For example: https://github.com/apache/db-jdo-site
> 
> The location of the DOAP is then added to the following file:
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
> Make sure you link to the raw blob.
> 
> 
>> Thanks,
>> Craig
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday September 7 1100 PDT 2000 CEST

2023-09-07 Thread Craig Russell

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

Next meeting: Thursday Sept 14 1100 PDT 2000 CET

Agenda:

1. No Description Of A Project for JDO
Craig is working on it. The authoritative file will go into the db-jdo-site
repo.

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

The EU Cyber Resilience Act is working its way through the legislative process
and the way it is currently worded has significant negative implications for
all open source projects, including all ASF projects.

Craig L Russell
c...@apache.org

DOAP for JDO

2023-09-06 Thread Craig Russell

Hi Sebb,

I've created a DOAP for the JDO project but I'm having some trouble putting it 
into the proper place. My svn is a bit rusty and I'm not even sure I'm trying 
to put it where it belongs.

Could you help? I think it's ready to go into 
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/committers
 but I'm not sure.

Thanks,
Craig


Craig L Russell
c...@apache.org

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

2023-08-31 Thread Craig Russell

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

Next meeting: Thursday September 7 1100 PDT 2000 CET

Agenda:

1. New DB PMC member: Tobias Bouschen

Congratulations Tobias!

2. No DOAP for JDO

This will need an update to the DOAP for DB to include JDO, Derby, and Torque.
AI Craig: update the DOAP file to include the three subprojects.

3. Signing releases using automated release infra is a possibility for us to
use for the next release.
AI Michael file a JDO JIRA to set up the necessary.
https://issues.apache.org/jira/browse/JDO-833

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

Final release candidate for JDK 21 is available as of August 24 2023.

8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version for JDO?
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

Craig L Russell
c...@apache.org

[ANNOUNCE] Member of DB PMC Tobias Bouschen

2023-08-29 Thread Craig Russell

Please join me in welcoming Tobias Bouschen as the latest member of the DB PMC.

Tobias has been contributing to JDO, writing pull requests, helping streamline 
the build process and providing valuable insight into project strategy 
especially with regard to JDK support.

He has been a committer since January 2021 and continues to be a valuable part 
of the JDO community.

Welcome, Tobias!

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday August 24 1100 PDT 2000 CET

2023-08-24 Thread Craig Russell

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

Next meeting: Thursday August 31 1100 PDT 2000 CET

Agenda:

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

Looks like we should investigate 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

Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday August 10 1100 PDT 2000 CET

2023-08-10 Thread Craig Russell

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

Next meeting: Thursday August 24 1100 PDT 2000 CET

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 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
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org


Craig L Russell
c...@apache.org

JDO TCK meeting Thursday August 10 1100 PDT 2000 CET

2023-08-03 Thread Craig Russell

Hi,

We will have our regular meeting Thursday August 10 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 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
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org

Minutes: JDO TCK meeting Thursday August 3 1100 PDT 2000 CET

2023-08-03 Thread Craig Russell

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

Next meeting: Thursday August 10 1100 PDT 2000 CET

Agenda:

1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
See email discussion with cdutz

Done. If any changes are still needed, we can discuss.

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

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

Merged and closed.

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
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday July 27 1100 PDT 2000 CEST

2023-07-27 Thread Craig Russell

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

Next meeting: Thursday August 3 1100 PDT 2000 CET

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

Defer until we have a release manager to look into the details.

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

Done. Good to go. Merged into main.

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
Craig L Russell
c...@apache.org

Craig L Russell
c...@apache.org

JDO TCK meeting Thursday August 3 1100 PDT 2000 CET

2023-07-27 Thread Craig Russell

Hi,

We will have our regular meeting Thursday August 3 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. 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 is a possibility for us to
use for the next release.

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
Craig L Russell
c...@apache.org
Craig L Russell
c...@apache.org

JDO TCK Conference Call Thursday July 27 1100 PDT 2000 CEST

2023-07-20 Thread Craig Russell

Hi,

We will have our regular meeting Thursday July 27 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
Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday July 20 1100 PDT 2000 CEST

2023-07-20 Thread Craig Russell

Attendees:

Next meeting: Thursday July 27 1100 PDT 2000 CET

Agenda:

1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
See email discussion with cdutz. We may be able to thread more results. Need to
look into removing the commit id from the subject. The list jdo-commits might
not have much useful information so it might be useful to unsubscribe from that
list.
Volunteer to investigate the jdo asf.yaml further.

2. Signing releases using automated release infra

For future reference, we may want to look into using a GitHub Action to prepare
release artifacts. This may reduce the number of steps in our release process,
but the energy required to set it up may be more than just do the process as it
exists.

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

Good progress. Still an issue with creating and disposing the URLClassLoader.
Not quite ready to merge.

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

Craig L Russell
c...@apache.org

Fwd: Signing releases using automated release infra

2023-07-18 Thread Craig Russell

Hi,

This is something worth discussing. It has the potential to significantly 
reduce the release manager's effort.

I'd guess that setting this up (once) is about the same complexity as 
performing a release (each time).

Any interest?

Craig

> Begin forwarded message:
> 
> From: Volkan Yazıcı 
> Subject: Signing releases using automated release infra
> Date: July 18, 2023 at 12:55:00 PDT
> To: d...@community.apache.org
> Reply-To: d...@community.apache.org
> 
> Abstract: Signing release artifacts using an automated release
> infrastructure has been officially approved by LEGAL. This enables
> projects to sign artifacts using, say, GitHub Actions.
> 
> I have been trying to overhaul the Log4j release process and make it
> as frictionless as possible since last year. As a part of that effort,
> I wanted to sign artifacts in CI during deployment and in a
> `members@a.o` thread[0] I explained how one can do that securely with
> the help of Infra. That was in December 2022. It has been a long,
> rough journey, but we succeeded. In this PR[1], Legal has updated the
> release policy to reflect that this process is officially allowed.
> Further, Infra put together guides[2][3] to assist projects. Logging
> Services PMC has already successfully performed 4 Log4j Tools releases
> using this approach, see its release process[4] for a demonstration.
> 
> [0] (members only!)
> https://lists.apache.org/thread/1o12mkjrhyl45f9pof94pskg55vhs61n
> [1] https://github.com/apache/www-site/pull/235
> [2] https://infra.apache.org/release-publishing.html#signing
> [3] https://infra.apache.org/release-signing.html#automated-release-signing
> [4] https://github.com/apache/logging-log4j-tools/blob/master/RELEASING.adoc
> 
> # F.A.Q.
> 
> ## Why shall a project be interested in this?
> 
> It greatly simplifies the release process. See Log4j Tools release
> process[4], probably the simplest among all Java-based ASF projects.
> 
> ## How can a project get started?
> 
> 1. Make sure your project builds are reproducible (otherwise there is
> no way PMC can verify the integrity of CI-produced and -signed
> artifacts)
> 2. Clone and adapt INFRA-23996 (GPG keys in GitHub secrets)
> 3. Clone and adapt INFRA-23974 (Nexus creds. in GitHub secrets for
> snapshot deployments)
> 4. Clone and adapt INFRA-24051 (Nexus creds. in GitHub secrets for
> staging deployments)
> 
> You might also want to check this[5] GitHub Action workflow for inspiration.
> 
> [5] 
> https://github.com/apache/logging-log4j-tools/blob/master/.github/workflows/build.yml
> 
> ## Does the "automated release infrastructure" (CI) perform the full release?
> 
> No. CI *only* uploads signed artifacts to Nexus. The release manager
> (RM) still needs to copy the CI-generated files to SVN, PMC needs to
> vote, and, upon consensus, RM needs to "close" the release in Nexus
> and so on.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 

Craig L Russell
c...@apache.org

A little help with git messages

2023-07-13 Thread Craig Russell

Hi Christofer,

We at the JDO project are concerned about the number of non-threaded messages 
in our jdo-commits list. We reconfigured our notifications in our asf.yaml but 
still get lots of un-threaded messages.

Could you spare 5 minutes and tell us what you think of our configuration?

jdo-comm...@db.apache.org

Thanks,
Craig

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday July 13 1100 PDT 2000 CEST

2023-07-13 Thread Craig Russell

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

Next meeting: July 20 11:00 PDT 20:00 CET

Agenda:

1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?

AI Craig ask cdutz to look at our mail lists

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

Done and done. AI Til resolve the ticket as fixed.

Having JNDI in the API disallows use with Android.
Volunteer needed to open a new JIRA for Android.

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

Looks good. Resolve as fixed.

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

Work in progress based on SonarCloud issue
Refactoring does make the code more readable.
Still more work to close the class loader once it is not needed for enhancement.

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

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

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

Craig L Russell
c...@apache.org

Fwd: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)

2023-07-07 Thread Craig Russell

There are over half a dozen messages regarding JDO-827/PR#81.

Is there a problem with the asf.yaml configuration that prevents these from 
being threaded?

I know we updated asf.yaml recently but somehow this does not meet my 
expectations.

Thanks,
Craig

> Begin forwarded message:
> 
> From: Tilmann 
> Subject: Re: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)
> Date: July 6, 2023 at 11:43:49 PDT
> To: apache/db-jdo 
> Cc: Subscribed 
> Reply-To: apache/db-jdo 
> 
> 
> 
> Merged #81  into main.
> 
> —
> Reply to this email directly, view it on GitHub 
> , or unsubscribe 
> .
> You are receiving this because you are subscribed to this thread.
> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday July 6 1100 PDT 2000 CEST

2023-07-06 Thread Craig Russell

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

Next meeting: Thursday July 13 11:00 PDT 20:00 CET

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

There is an implementation of JNDI that we use as a default. Final review
before merge. Keep the "old" JNDI implementation as a comment in the properties
file and add a new comment stating what it is.

We no longer need the command line option jdo.tck.skipJndi. This option can be
removed.
AI Michael write a JIRA to remove the option after discussion.

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

Still working on tck changes. Some differences from api project.

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

Wait for JDO-830

4. sonarcloud issues

JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

* Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false=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
Wait until LTS JDK 21 in September

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

7. Other issues

SonarCloud reports an issue with the logging context class loader:
https://sonarcloud.io/project/issues?resolved=false=BUG=db-jdo=AYicN6l1vjmVlbkR1n8S=code

Volunteer needed.

Action Items from weeks past:

Craig L Russell
c...@apache.org

Re: Updates for our July report to the board?

2023-06-29 Thread Craig Russell

Hi Bryan,

Thanks for taking care of this.

Status of JDO is ongoing, low activity.
No new releases since the last report.
No changes to roster.

The JDO project is continuing to work on improving support for current and 
future JDKs. Currently supporting JDK 7, 11, and 17. Looking to JDK 21 for the 
next supported (continuous testing platform) release. We are also upgrading the 
JUnit dependency from JUnit 3 to JUnit 5 so we can more easily take advantage 
of potential performance improvements.

Warm regards,
Craig

> On Jun 29, 2023, at 07:04, Bryan Pendleton  wrote:
> 
> Hi all, it's time for our quarterly report, please let me
> know of any updates about community activities in
> April-June that we should include!
> 
> Our report isn't due for another 2 weeks, but I'll
> be away from keyboard for the next week so I'm
> starting early :)
> 
> thanks,
> 
> bryan

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday June 29 1200 PDT 2100 CEST

2023-06-29 Thread Craig Russell

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

Next meeting: Thursday July 6 11:00 PDT 20:00 CET

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

Good to go.

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

Not ready for review.

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

To be considered after 829 and 830 are merged.

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

Tilmann has implemented a simple Mock JNDI class that allows the TCK to run,
including the JNDI dependent tests.
https://github.com/apache/db-jdo/pull/81

This will be the default used when running the TCK. If users prefer to use a
fuller implementation (e.g. providerutil), they will need to update one
configuration file that names the JNDI implementation.

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

repository.apache.org under apache.org domain to release software
seems to be automatically synchronized with nexus repo

Any items for the July board report?

Status of JDO is ongoing, low activity.
No new releases since the last report.

The JDO project is continuing to work on improving support for current and
future JDKs. Currently supporting JDK 7, 11, and 17. Looking to JDK 21 for the
next supported release. We are also upgrading the JUnit dependency from JUnit 3
to JUnit 5 so we can more easily take advantage of potential performance
improvements.

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

Craig L Russell
c...@apache.org

Reschedule June 29 meeting?

2023-06-27 Thread Craig Russell

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

Minutes: JDO TCK Conference Call Thursday June 15 1100 PDT 2000 CEST

2023-06-15 Thread Craig Russell

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

Next meeting: Thursday June 29 1100 PDT 2000 CET

Agenda:

1. New JUnit JIRAs
JDO-829: "api: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-829

Some test classes that inherit from JUnit classes no longer need the superclass.
Some message print methods have different signatures.
Negative tests can be simplified with JUnit 5. No longe method.r need
try/catch; just need the assert call.

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

Many more tests compared to the api project. Will defer until api is done.

Whatabout exectck? Needs investigation.

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

This will need to wait until the other JIRAs (JDO-829 and JDO-830) are done.

Parameterized tests in JUnit 5 might be useful.
Test suites might make sense in light of configurations.

Suggestion from IntelliJ SonarLint plugin: make test classes and the test
methods package protected instead of public.

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

Recent statistics on JDK usage:
https://newrelic.com/resources/report/2022-state-of-java-ecosystem

Tobias added JDK20 to the set of JDKs to use for the tests. Results:

https://github.com/tobous/db-jdo/commit/a01db959898bfb0cd84b99f0510840c87704bba9

https://github.com/tobous/db-jdo/actions/runs/5170691272/jobs/9313757782

https://pipelines.actions.githubusercontent.com/serviceHosts/7b725ad1-bed5-4727-8ea3-c12c930e4e15/_apis/pipelines/1/runs/5/signedlogcontent/9?urlExpires=2023-06-15T18%3A39%3A40.4008195Z=HMACV1=8zWoLaZw2erGFoYbhDA%2B9%2FCQYgrj95FpN780xuGXu7k%3D

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

Still an objective once we have a major release planned.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday June 8 1100 PDT 2000 CEST

2023-06-08 Thread Craig Russell

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

Next meeting: Thursday June 15 1100 PDT 2000 CET

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

PRs look good. Possible issue with mails from SonarCloud; can these be
disabled? The results we are mostly looking for are displayed as comments in
the PR anyway so a separate notice is not really needed.

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

Good to go.

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

Volunteer needed to analyze the alternatives. Originally opened for Android
support.

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

Wait until JDK 21 (LTS) to make any more changes.

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

Since this is a breaking change, we should look at releasing what we have
before making the move. Many Java users are still on JDK 8.

7. Other issues

Java Records might be interesting to support in JDO.
https://openjdk.org/jeps/395

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday June 1 1100 PDT 2000 CEST

2023-06-01 Thread Craig Russell

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

Next meeting: Thursday June 8 1100 PDT 2000 CET

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

update on [May 03 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade 
tests for multithreaded

Perhaps the best way to start is to first modify the API module to use JUnit 5.
Currently tests are written in the vintage JUnit 3 interface. 
https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build
AI: perhaps best to split the JIRA-to-be into a few: first for upgrading JUnit; 
next for the API and next for the TCK.

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




Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Wednesday May 24 1200 PDT 2100 CEST

2023-05-24 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Thursday June 1 1100 PDT 2000 CET

Agenda:

1. Github settings in .asf.yaml (see email from Craig)

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

We should try out these configuration settings.
AI Tobias: write a JDO JIRA and GitHub PR to see what happens.

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

AI Volunteers respond to JIRA 827. Keep on the agenda.

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

Official supported release of JDK 20 was released March 2023.
AI Tobias add JDK 20 to the build request for GitHub for testing.

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

Craig L Russell
c...@apache.org

Re: Mailing list configurations for discussion

2023-05-18 Thread Craig Russell

> On May 18, 2023, at 08:27, Tilmann Zäschke  wrote:
> 
>> https://community.apache.org/contributors/mailing-lists
> 
> That looks good to me. Since these are just .asf.yam setting, I suppose it 
> should be easy to just try it out?

Yes, I'd be ok with trying it out and tweaking it if we have issues. I have 
noticed that the GH notices that we get are not threaded to make it easy to 
follow.

So anything could be better. Feel free to make a PR or just push to main and 
see what happens.

Best,
Craig
> 
> Best,
> Til
> 
> On 18/05/2023 02:37, Craig Russell wrote:
>> Take a look at this:
>> 
>> https://community.apache.org/contributors/mailing-lists
>> 
>> It may make sense for us to re-examine our mail lists, notifications, etc.
>> 
>> WDYT?
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Mailing list configurations for discussion

2023-05-17 Thread Craig Russell

Take a look at this:

https://community.apache.org/contributors/mailing-lists

It may make sense for us to re-examine our mail lists, notifications, etc.

WDYT?
Craig

Craig L Russell
c...@apache.org

Github settings in .asf.yaml

2023-05-16 Thread Craig Russell

What do you think about these settings? Other projects have used them to 
simplify the stream of messages on dev related to PRs, comments, etc.

These go in the .asf.yaml file:

 # Attempt to make the auto-generated github emails more easily readable in 
email clients.
  custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
new_discussion: "[D] {title} ({repository})"
edit_discussion: "Re: [D] {title} ({repository})"
close_discussion: "Re: [D] {title} ({repository})"
close_discussion_with_comment: "Re: [D] {title} ({repository})"
reopen_discussion: "Re: [D] {title} ({repository})"
new_comment_discussion: "Re: [D] {title} ({repository})"
edit_comment_discussion: "Re: [D] {title} ({repository})"
delete_comment_discussion: "Re: [D] {title} ({repository})"

Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Thursday May 11 1100 PDT 2000 CEST

2023-05-11 Thread Craig Russell

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

Next meeting: Thursday May 18 1100 PST 2000 CET

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

Good to go.

* Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo

Good to go.

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

We are using a very old JUnit version. We use JUnit 3 API with a special
interface that allows us to use JUnit 5. With the actual JUnit 5 API we can
consider using multi-thread tests for read-only tests which might save
significant time.

Other ideas include grouping tests together that use the same schema.

JNDI is not available in the Android environment.
AI Tilmann: file a JIRA

Action Items from weeks past:

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Wednesday May 3 1200 PDT 2100 CEST

2023-05-03 Thread Craig Russell

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

Next meeting: Thursday May 11 1100 PDT 2000 CET

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
 

Prioritize methods in the API.
JDOHelper.getObjectState
JDOHelper.getPersistenceManagerFactory (big catch clauses)

 * 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

Possible issue with Android support.

4. Other issues

Is there a reason to try to improve the test framework? We use vintage JUnit 
(based on JUnit 4). Some ideas:
Migrate to JUnit 5.
Set up the database once for many tests; run read-only tests with the same 
setup.
Set up the database once for many tests; run read-only tests multithreaded 
https://www.baeldung.com/junit-5-parallel-tests

Could we adapt JDO to support newer database implementations?
https://www.datanucleus.org/products/accessplatform_4_1/jdo/samples/tutorial_cassandra.html

AI volunteer make a JIRA or two: migrate to JUnit 5; upgrade tests for 
multithreaded 

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


Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Wednesday April 26 1200 PDT 2100 CEST

2023-04-26 Thread Craig Russell

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

Next meeting: Wednesday May 3 1200 PDT 2100 CET

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

Thanks, Tobias. 
Good to go. 
Merged.

  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

Volunteers needed.

* Raw types should not be used:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo

Volunteers needed.

2. field/property converters

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

The Javadoc has been updated to remove references. Good to close this one as 
well.

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

LTS versions are Java 8, 11, 17, and 20. We need to decide the next version to 
support.

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday April 20 1100 PDT 2000 CEST

2023-04-20 Thread Craig Russell

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

Next meeting: Wednesday April 26 1200 PDT 2100 CEST

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

The current behavior is better than the suggested fix. 
Mark printStackTrace as Won't Fix.
Fix the non-final nested and failed.
AI Tobias: new PR to fix the two.

  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

Volunteers needed.

* Raw types should not be used:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo

Breaking change; keep on the agenda.

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

Good to go.
This makes it clear that we are not looking at changing it.

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

Craig L Russell
c...@apache.org

Fwd: Minutes: JDO TCK Conference Call Thursday April 6 1100 PDT 2000 CEST

2023-04-07 Thread Craig Russell

Hi Bryan,

We discussed the quarterly report yesterday.

Warm regards,
Craig

> Begin forwarded message:
> 
> From: Craig Russell 
> Subject: Minutes: JDO TCK Conference Call Thursday April 6 1100 PDT 2000 CEST
> Date: April 6, 2023 at 11:57:19 PDT
> To: JDO Project 
> 
> 1. Updates for our quarterly report to the board?
> 
> JDO project is working on sonar cloud reports that will improve the quality 
> of the code. We have already fixed reports under the category of Reliability 
> and Security. Still working on Maintainability.

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday April 6 1100 PDT 2000 CEST

2023-04-06 Thread Craig Russell

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

Next meeting: Thursday April 20 1100 PDT 2000 CET

Agenda:

1. Updates for our quarterly report to the board?

JDO project is working on sonar cloud reports that will improve the quality of
the code. We have already fixed reports under the category of Reliability and
Security. Still working on Maintainability.

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;

Looks good. AI Til: merge to main.

* Cognitive Complexity of methods should not be too high:

https://sonarcloud.io/project/issues?resolved=false=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo

Volunteer needed to pick up one of these and start a discussion.

* Raw types should not be used:

https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo

In FetchPlan 186 getDetachmentRoots the return type is Collection. Perhaps
change this to Collection. Might be a breaking change.
AI Michael: give it a try.

JDOException.inPrintStackTrace is modified during the execution of the method.
This is to enable catching multiple exceptions and presenting them to the user.
AI Tobias: create a PR for discussion

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

Til wrote a test case and submitted it to DataNucleus. Implementation is not
resourced.
The JDO Javadoc says this should work but it does not.
Volunteer needed to update the Javadoc.
AI Til write a new JIRA needed just for the Javadoc update.

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.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO
development and see if and how they want to be recognized on the JDO and DB web
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

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

2023-04-04 Thread Craig Russell

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 commit to branch clr-apache-array-copy
>>>>> in repository https://gitbox.apache.org/repos/asf/db-jdo.git
>>>>> 
>>>>> commit 034060cb69ad0a10f9bdf5aca4d5a0c9c9c11e8c
>>>>> Author: Craig L Russell

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

2023-04-03 Thread Craig Russell

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

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

2023-04-03 Thread Craig Russell

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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday March 30 1100 PDT 2000 CEST

2023-03-30 Thread Craig Russell

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

Next meeting: Thursday April 6 1100 PDT 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823
Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

* 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

RunTCK: Still need a volunteer to look at the very complex method.
 
* Type parameter names should comply with naming convention:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS119=CODE_SMELL=db-jdo

Resolve: make the parameter S; update javadoc if necessary. 
AI Michael

* Unused local variables should be removed:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1481=CODE_SMELL=db-jdo

Utilities.createReaderThread has unused variables count and outputBytesRead
AI Tilmann try removing the unused variables

* 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

See other email. Proposed change: Collection to List and change 
implementations to remove loop.

[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

Craig L Russell
c...@apache.org

Proposal for code smell Use ... "Collections.addAll" or "System.arraycopy" instead.

2023-03-30 Thread Craig Russell

Two methods with different names but identical implementation:
public static void string2Set(String names, Collection list)
public static void string2List(String names, List list)

The behavior only depends on the actual type of the "list" parameter.

Proposal: change implementations of both methods from iterating over the split 
list of the argument to use the addAll of the second parameter

Both methods are used in the TCK:

clr% grep -R "string2Set" .
./exectck/src/main/java/org/apache/jdo/exectck/RunTCK.java:
PropertyUtils.string2Set(dblist, dbs);
./exectck/src/main/java/org/apache/jdo/exectck/RunTCK.java:
PropertyUtils.string2Set(identitytypes, idtypes);
./exectck/src/main/java/org/apache/jdo/exectck/InstallSchema.java:
PropertyUtils.string2Set(cfgList, cfgs);
./exectck/src/main/java/org/apache/jdo/exectck/InstallSchema.java:  
PropertyUtils.string2Set(cfgList, cfgs);
./exectck/src/main/java/org/apache/jdo/exectck/InstallSchema.java:
PropertyUtils.string2Set(dblist, dbs);
./exectck/src/main/java/org/apache/jdo/exectck/InstallSchema.java:
PropertyUtils.string2Set(identitytypes, idtypes);
./exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java:  public 
static void string2Set(String names, Collection list) {
./exectck/src/main/java/org/apache/jdo/exectck/Enhance.java:
PropertyUtils.string2Set(identitytypes, idtypes);

clr% grep -R "string2List" .
./exectck/src/main/java/org/apache/jdo/exectck/RunTCK.java:
PropertyUtils.string2List(cfgList, (List) cfgs);
./exectck/src/main/java/org/apache/jdo/exectck/RunTCK.java:  
PropertyUtils.string2List(cfgList, (List) cfgs);
./exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java:  public 
static void string2List(String names, List list) {

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday March 23 1200 PDT 2000 CET

2023-03-23 Thread Craig Russell

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

Next meeting: Thursday March 30 1100 PDT 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

* Arrays should not be be copied using loops:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3012=CODE_SMELL=db-jdo

In exectck PropertyUtils look at the method names and parameter names and 
javadoc for string2Set and string2List.

AI Craig: fix it. PR referencing JDO-823

* Arrays should not be created for varargs parameters:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3878=CODE_SMELL=db-jdo

JDOImplHelper.construct is too complicated.
AI Michael: fix it. JDO-823

* 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

JDOImplHelper.assertOnlyKnownStandardProperties 1168
AI Michael resolve as won't fix

exectck.runTCK longest method in history
Leave alone for now and look again when we restructure the runTCK method.
Volunteer needed.

* Mutable fields should not be "public static":
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS2386=CODE_SMELL=db-jdo

JDOImplHelper.USER_CONFIGURABLE_STANDARD_PROPERTIES
Breaking change. 
AI Michael resolve as false positive

 * 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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday March 16 1200 PDT 2000 CET

2023-03-16 Thread Craig Russell

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

Next meeting: Thursday March 23 1200 PDT 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

* Standard outputs shoudl not be used to log anything:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS106=MAJOR=CODE_SMELL=db-jdo
InstallSchema won't fix
Enhancer won't fix
JDOException remove the offending printStackTrace() which will use the 
superclass implementation 
AI Michael

* Unsed type parameters shoudl be removed:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS2326=MAJOR=CODE_SMELL=db-jdo
EnumExpression has unused type T breaking change mark won't fix until 3.0
At the time we change this we will also need a TCK test
Volunteer needed

* Exception classes should be immutable:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1165=MINOR=CODE_SMELL=db-jdo
JDOException fields nested and failed should be marked final
AI Tobias
inPrintStackTrace is modified during the execution of the method 
AI Tobias look into it; maybe already a test case to try

* 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

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday March 9 1100 PST 2000 CET

2023-03-09 Thread Craig Russell

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

Next meeting: Thursday March 16 1200 PDT 2000 CET

Agenda:

1. New PR #69 "Removed nested try-catch" 
https://github.com/apache/db-jdo/pull/69

A couple of comments but otherwise good to go.

2. new PR #70 "JDO-825: Improve exectck classes" 
https://github.com/apache/db-jdo/pull/70

Looks good. Fixes a couple more issues as well.

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

Sections of code should not be commented out: 
https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo

False  positive.

Throwable and Error should not be caught: 
https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo

Should be fixed to catch Exception instead of catching Error.
AI Til.

Constructors of an abstract" class should not be declared "public": 
https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=db-jdo

Should be fixed to declare the constructor for SingleFieldIdentity to protected
AI Michael.

Cognitive Complexity of methods should not be too high: 
https://sonarcloud.io/project/issues?resolved=false=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo

Should be looked at in more detail.
Volunteers needed.

Raw types should not be used: 
https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo

Potential breaking changes so defer to 3.0 release.

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

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

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

5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651


Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET

2023-03-01 Thread Craig Russell

well, dunno how that happened. the jdo meeting is in progress with just me

> On Mar 1, 2023, at 12:07, Tilmann Zäschke  wrote:
> 
> I am getting "the host has another meeting in progress" ...?
> 
> 
> On 01/03/2023 18:57, Tobias Bouschen wrote:
>> Hi all,
>> 
>> sorry for the short notice again, but I won't be able to attend today's 
>> conference call. I will see you all next week.
>> 
>> Best regards,
>> Tobias
>> 
>> On 28/02/2023 20:58, Michael Bouschen wrote:
>>> Hi,
>>> 
>>> We will have our regular meeting Wednesday March 1 12:00 Pacific Standard 
>>> Time (PST) 21:00 Central European Time (CET) to discuss JDO TCK issues and 
>>> status.
>>> 
>>> We use the following dial-in for audio and video:
>>> https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 
>>> 
>>> Agenda:
>>> 
>>> 1. JIRA JDO-819 "Code quality analysis" 
>>> https://issues.apache.org/jira/browse/JDO-819
>>>JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
>>> https://issues.apache.org/jira/browse/JDO-823
>>> 
>>> Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo
>>> 
>>>  * Try-catch blocks should not be nested:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo
>>>  
>>>  * Utility classes should not habe public constructors:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo
>>>  
>>>  * Sections of code should not be commented out:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo
>>>  
>>>  * Throwable and Error shoudl not be caught:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo
>>>  
>>>  * Constructors of an abstract" class should not be declared "public":
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS5993=MAJOR=db-jdo
>>>  
>>>  * Cognitive Complexity of methods should not be too high:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo
>>>  
>>>  * Raw types should not be used:
>>> https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo
>>>  
>>> 
>>> 2. JIRA JDO-709 "Standardize field/property converters" 
>>> https://issues.apache.org/jira/browse/JDO-709
>>> 
>>> 3. JIRA JDO-822: "Verify compatibility with JDK 20" 
>>> https://issues.apache.org/jira/browse/JDO-822
>>> 
>>> 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
>>> https://issues.apache.org/jira/browse/JDO-812
>>> 
>>> 5. Other issues
>>> 
>>> Action Items from weeks past:
>>> 
>>> [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
>>> JDO-709.
>>> [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
>>> annotations and results of the test.
>>> [Dec 09 2021] AI Craig: Try to contact all current/former participants in 
>>> JDO development and see if and how they want to be recognized on the JDO 
>>> and DB web sites.https://db.apache.org/whoweare.html
>>> [Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
>>> members asking if they wish to continue.
>>> [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
>>> accounts
>>> [Oct 17 2014] AI Matthew any updates for "Modify specification to address 
>>> NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651
>>> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday February 23 1100 PST 2000 CET

2023-02-23 Thread Craig Russell

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

Next meeting: Wednesday 1200 PST 2100 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

* Cognitive Complexity of methods should not be too high:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo
* Generic exceptions should never be thrown
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS112=MAJOR=db-jdo

In JDOHelper.invoke, change throw RuntimeException to throw 
JDOFatalInternalException with UnexpectedException
In exectck/Utilities.invokeTest, "won't fix".

* Try-catch blocks should not be nested:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1141=MAJOR=db-jdo
* Utility classes should not habe public constructors:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1118=MAJOR=db-jdo
* Sections of code should not be commented out:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS125=MAJOR=db-jdo
* Throwable and Error shoudl not be caught:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1181=MAJOR=db-jdo

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

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

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

5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday February 16 1100 PST 2000 CET

2023-02-16 Thread Craig Russell

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

Next meeting: Thursday February 23 1100 PST 2000 CET

Agenda:

1. Upcoming global changes to default GitHub Actions behavior for outside 
collaborators

Because of possible security issues, ASF's use of GitHub Actions will be 
further limited for people who are not "approved". 

Nothing needed for JDO for now.

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

* Generic wildcard types should not be used in return types:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS1452=CRITICAL=db-jdo

For example: a query API that returns NumericExpression
AI Michael: Resolve as "won't fix" // breaking change

* Cognitive Complexity of methods should not be too high:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS3776=CRITICAL=db-jdo

Breaking code into smaller pieces does not necessarily reduce complexity.
Defer to future discussion.

* Standard outputs should not be used directly to log anything:
  
https://sonarcloud.io/project/issues?resolved=false=java%3AS106=MAJOR=CODE_SMELL=db-jdo

AI Michael: Resolve as "won't fix" // most of these are in console oriented 
maven tasks

* Track uses of "TODO" tags:
  https://sonarcloud.io/project/issues?resolved=false=INFO=db-jdo

AI Michael: Resolve by either removing the comment or removing "TODO"

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:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Wednesday February 8 1200 PST 2100 CET

2023-02-11 Thread Craig Russell

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

Next meeting: Thursday February 16 1100 PDT 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

Complaints about use of System.out and System.error might just be marked as 
"won't fix". Worth examining.

Also use of generics needs to be looked into.

Some 8 cases of // TODO in annotations (default value for boolean)

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

Andy: this feature was never requested by any other user and has not been 
implemented in DataNucleus... 

Volunteers needed. Both for DN and 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:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651


Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Thursday February 2 1100 PST 2000 CET

2023-02-02 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Thursday February 9 1200 PST 2100 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo 
<https://sonarcloud.io/summary/overall?id=db-jdo>

Some candidate code smells to be discussed:
https://sonarcloud.io/project/issues?resolved=false=java%3AS1948=CRITICAL=db-jdo
1. JDOException class contains an Object. Solution: make the field transient
2. SingleFieldIdentity class contains Object keyAsObject.
AI: Tobias look at solutions. 
There is a case where a user-defined type could be the key. 
Solution: Leave it as is and mark it as "won't fix".
3. InstanceLifeCycleEvent contains Object target. Solution: make the field 
transient.

https://sonarcloud.io/project/issues?resolved=false=java%3AS2692=CRITICAL=db-jdo
Looks like a false positive.

https://sonarcloud.io/project/issues?resolved=false=java%3AS1192=CRITICAL=db-jdo
file JDOConstants has two properties PROPERTY_ENHANCER_VENDOR_NAME and 
PROPERTY_ENHANCER_VERSION_NUMBER
"Fixing" this would be a breaking change, so mark as "will not fix".

https://sonarcloud.io/project/issues?resolved=false=java%3AS1214=CRITICAL=db-jdo
Won't fix.

https://sonarcloud.io/project/issues?resolved=false=java%3AS127=MAJOR=db-jdo
public class Enhancer: Refactor the code in order to not assign to this loop 
counter from within the loop body 
Won't fix.

https://sonarcloud.io/project/issues?
resolved=false=java%3AS112=MAJOR=db-jdo
AI Michael: Look at solutions

https://sonarcloud.io/project/issues?resolved=false=java%3AS1185=MINOR=db-jdo
Removing this method would also remove the javadoc. 
Resolution: won't fix.

https://sonarcloud.io/project/issues?resolved=false=java%3AS1481=MINOR=db-jdo
Leave as is. 
Resolution: won't fix.

AI Michael: merge fixes to main.

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

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

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

5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday January 26 1100 PST 2000 CET

2023-01-26 Thread Craig Russell

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

Next meeting: 

Agenda:

1. Copyright notice is out of date

There are two NOTICE files. Only one is really needed. The NOTICE in the tck 
package is only needed if there is an independent distribution of the tck. 
[Til removed the errant file in December 2022.] All good. 

AI Michael Update NOTICE file in jdo root directory.
Done.

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

AI Michael prepare a list of candidate code smells

  Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo 
<https://sonarcloud.io/summary/overall?id=db-jdo>

3. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709
Til has created a DataNucleus test case that still needs work: 
https://github.com/tzaeschke/test-jdo

Clone the branch and do mvn clean install to see the result.

Volunteers needed to review Til's test case. Currently two tests: one should 
fail until the feature is implemented but both fail. 

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:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Re: Copyright notice is out of date

2023-01-21 Thread Craig Russell

I believe that the NOTICE.txt in the tck is only there if the tck is 
distributed independently. Otherwise, it should be removed.

> On Dec 7, 2022, at 20:47, Craig Russell  wrote:
> 
> The copyright notice is in two places:
> 
> 
> ./NOTICE:Copyright 2005-2022 The Apache Software Foundation
> ./tck/NOTICE.txt:Copyright 2005-2006 The Apache Software Foundation
> 
> The NOTICE.txt in tck might be historic. Do we need it?
> 
> Craig
>> On Dec 6, 2022, at 17:07, Craig Russell  wrote:
>> 
>> I noticed this while reviewing the http https patch (hat tip Til). The 
>> copyright NOTICE is out of date.
>> 
>> I'll write a patch which includes both the copyright notice and updated 
>> instructions for release.
>> 
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Wednesday January 18 1200 PST 2100 CET

2023-01-18 Thread Craig Russell

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

Next meeting: Thursday January 26 1100 PST 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823
  Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

This is a work in progress. Volunteers welcome to look at issues and propose 
patches.

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

Volunteers needed to pursue this. Needs changes to code and/or documentation. 
Most of the discussion is in the conference call thread. Til has created a 
DataNucleus test case that still needs work;
https://github.com/tzaeschke/test-jdo contains a test case.
https://github.com/tzaeschke/test-jdo/tree/master/src/test/java/org/datanucleus/test
https://github.com/datanucleus/test-jdo/compare/master...tzaeschke:test-jdo:master

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

Regards Michael


Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday January 12 1100 PST 2000 CET

2023-01-12 Thread Craig Russell

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

Next meeting: Wednesday  January 18 1200 PST 2100 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823
New PR #67 https://github.com/apache/db-jdo/pull/67

One quirk with the tool: it only rescans when the PR is merged. Ok to merge and 
see what is left. Merged now. SonarCloud reports no blockers and only 161 code 
smells left.And 56 code smells are regarding using System.out or System.error.

Perhaps we can reconfigure "cognitive complexity" to increate the complexity 
and thereby reduce the number of complaints. The biggest method seems to be 400 
LOC exectck. 

3 cases of a serializable class having no specific serialize/deserialize 
methods but containing non-serializable fields. 

Volunteers needed to investigate other code smells.

https://sonarcloud.io/summary/overall?id=db-jdo

2. New JIRA JDO-824 "JDOImplHelper.nonBinaryCompatibleMakeDirty() ignores 
Throwable" https://issues.apache.org/jira/browse/JDO-824

Proposal: close as "will not fix". SonarCloud did not flag it because the catch 
has a comment. 
AI Til update the JIRA with summary of our discussion and close.

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

No progress.

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

Volunteer needed to try to compile and run TCK with JDK 20. Not yet GA.
Derby had some issues with JDK 20:
https://issues.apache.org/jira/browse/DERBY-7149

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:

[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

Regards Michael


Craig L Russell
c...@apache.org

Re: Topics for our January report to the board?

2023-01-10 Thread Craig Russell

Hi Bryan,

Thanks for the reminder. 

No JDO releases since 3.2.1 last quarter.

The JDO project is working on improving code quality via feedback solicited 
from a code analysis tool called SonarCloud. SonarCloud itself is not open 
source but is free to analyze open source projects. A number of issues reported 
by the tool have been merged to the main branch and several others are 
currently being worked.

The JDO project has a dependency on Derby to run the Technology Compatibility 
Kit and we have analyzed the recent Derby security vulnerability. We have 
determined that our use of Derby does not expose the project to any attacks and 
thus we have no immediate plans to update our dependency.

We are discussing whether to continue to support JDK 8 as the lowest level or 
move to JDK 11. This would be a breaking change so we are not considering it 
prior to a significant release: 3.3.

Best,
Craig

> On Jan 10, 2023, at 04:45, Bryan Pendleton  wrote:
> 
> Apparently, during the holiday season, I forgot about our reporting
> schedule, and our quarterly report to the board is due tomorrow.
> 
> Please let me know of any topics we should include in our January report.
> 
> thanks,
> 
> bryan

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday January 5 1100 PST 2000 CET

2023-01-05 Thread Craig Russell

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

Next meeting: Thursday January 12 1100 PST 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823

One code smell is declaring final constants in interfaces. JDO interface 
Constants declares a large number of constants that are used throughout. 
Proposal to avoid code breaking: define a JDOConstants class that can be 
imported. But this doesn't solve the code smell. Alternate proposal: since 
JDOHelper already implements Constants, we can change usages of CONSTANT_NAME 
to JDOHelper.CONSTANT_NAME
AI Michael: change all usages of Constants to use JDOHelper.CONSTANT_NAME 
instead of CONSTANT_NAME. The code smell will remain but the problem will be 
fixed.

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 see what else is needed to have the analysis 
integrated into GitHub repo.
[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

Regards Michael


Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday December 29 1100 PST 2000 CET

2022-12-29 Thread Craig Russell

Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Thursday January 5 1100 PST 2000 CET

Agenda:

1. Derby vulnerability
See https://issues.apache.org/jira/browse/DERBY-7147

This is a vulnerably without a known exploit. The only use of Derby in JDO is 
in the TCK tests. The Derby fix is not yet available, and will only be 
available for Java 17. So no action for JDO.

2. JIRA JDO-821: "Fix sonarcloud issues of type Bugs" 
https://issues.apache.org/jira/browse/JDO-821
JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819

Just two issues left:
When catching an interrupt, the exception is "swallowed" by a RuntimeException. 
AI Michael: merge fix to main.
When printing stack traces, we synchronize on the output stream. Will not fix.

Other issues are SonarCloud "Code Smell" which should be looked at more 
closely.'
Whenever a collection of issues is going to be fixed, we should create a new 
JIRA and link it to "parent" JDO-819. Once we have reached "will not fix" for 
all remaining issues we can close JDO-819.

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

No update. Waiting for DataNucleus and/or reporter.

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

A volunteer can see if the TCK runs on JDK 20 but not high priority since JDO 
20 is not expected to be Long Term Support.

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:

[Nov 23 2022] AI Tilmann see what else is needed to have the analysis 
integrated into GitHub repo.
[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

Regards Michael


Craig L Russell
c...@apache.org

Re: Minutes: JDO TCK Conference Call Thursday December 15 1100 PST 2000 CET

2022-12-16 Thread Craig Russell

Hi Til,

Marking the issue as false positive seems to be better than modifying the code.

I'm also thinking that SonarCloud might pay more attention to false positives 
than to NOSONAR in the code...

Craig

> On Dec 16, 2022, at 08:05, Tilmann  wrote:
> 
> 
> > 4. JIRA JDO-819 "Code quality analysis"
> https://issues.apache.org/jira/browse/JDO-819
> <https://issues.apache.org/jira/browse/JDO-819>
> 
> I forgot to mention, instead of '// NOSONAR' it is also easily possible
> to mark problems as "false positive" in the web UI.
> 
> In my opinion this would be preferred over '// NOSONAR' because using
> the web UI avoids cluttering the code with '// NOSONAR' statements.
> 
> Maybe something to discuss in the next meeting.
> 
> Best,
> 
> Til
> 
> 
> On 16.12.22 16:49, Craig Russell wrote:
>> Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
>> 
>> Next meeting: Thursday December 29 1100 PST 2000 CET
>> 
>> Agenda:
>> 
>> 1. Derby vulnerability
>> See https://issues.apache.org/jira/browse/DERBY-7147 
>> <https://issues.apache.org/jira/browse/DERBY-7147>
>> 
>> No rush to upgrade Derby from 10.14.2 (current JDO dependency for tck) to 
>> 10.14.3 (fixed version). The tck does not use LDAP which is the attack 
>> vector.
>> AI Michael look into upgrading.
>> 
>> 2. JIRA JDO-820: "Clean up copyright NOTICE and references": 
>> https://issues.apache.org/jira/browse/JDO-820
>> Ist there anything left?
>> Nothing left. Resolved.
>> 
>> Which Fix Version do we want to use?
>> Next version whatever that is. 3.2.2 and 3.3
>> 
>> 3. JIRA JDO-821: "Fix sonarcloud issues of type Bugs" 
>> https://issues.apache.org/jira/browse/JDO-821
>> See PR #65: https://github.com/apache/db-jdo/pull/65 
>> <https://github.com/apache/db-jdo/pull/65>
>> 
>> 4. JIRA JDO-819 "Code quality analysis" 
>> https://issues.apache.org/jira/browse/JDO-819 
>> <https://issues.apache.org/jira/browse/JDO-819>
>> 
>> Changes in PR#65 can be merged.
>> Tilmann is looking at the SonarCloud "security" issues. Seem to be innocuous.
>> 
>> Still more SonarCloud issues (code smell) to address. For example:
>> https://sonarcloud.io/project/issues?issues=AYTeBPbL_-S9Jt7nsSUW=AYTeBPbL_-S9Jt7nsSUW=db-jdo
>>  
>> <https://sonarcloud.io/project/issues?issues=AYTeBPbL_-S9Jt7nsSUW=AYTeBPbL_-S9Jt7nsSUW=db-jdo>
>> 
>> Every subclass of JDOUserException smells. Not really an issue for us.
>> 
>> Anyone who looks into a SonarCloud issue should add a comment to the JDO-819 
>> JIRA with the analysis and resolution and possibly a PR. At some point we 
>> may close the issue after the items are low enough importance.
>> 
>> 5. JIRA JDO-709 "Standardize field/property converters" 
>> https://issues.apache.org/jira/browse/JDO-709
>> 
>> 6. JIRA JDO-815 "Change headers on source files to use https:// instead of 
>> http:// " https://issues.apache.org/jira/browse/JDO-815 
>> <https://issues.apache.org/jira/browse/JDO-815>
>> 
>> Ready to resolve.
>> AI Craig resolve it.
>> 
>> 7. JIRA JDO-822: "Verify compatibility with JDK 20" 
>> https://issues.apache.org/jira/browse/JDO-822 
>> <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:
>> 
>> [Nov 23 2022] AI Tilmann see what else is needed to have the analysis 
>> integrated into GitHub repo.
>> [Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
>> JDO-709.
>> [Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
>> annotations and results of the test.
>> [Dec 09 2021] AI Craig: Try to contact all current/former participants in 
>> JDO development and see if and how they want to be recognized on the JDO and 
>> DB web sites.https://db.apache.org/whoweare.html
>> [Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
>> members asking if they wish to continue.
>> [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
>> [Oct 17 2014] AI Matthew any updates for "Modify specification to address 
>> NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday December 15 1100 PST 2000 CET

2022-12-16 Thread Craig Russell

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

Next meeting: Thursday December 29 1100 PST 2000 CET

Agenda:

1. Derby vulnerability
See https://issues.apache.org/jira/browse/DERBY-7147
<https://issues.apache.org/jira/browse/DERBY-7147>

No rush to upgrade Derby from 10.14.2 (current JDO dependency for tck) to
10.14.3 (fixed version). The tck does not use LDAP which is the attack vector.
AI Michael look into upgrading.

2. JIRA JDO-820: "Clean up copyright NOTICE and references":
https://issues.apache.org/jira/browse/JDO-820
Ist there anything left?
Nothing left. Resolved.

Which Fix Version do we want to use?
Next version whatever that is. 3.2.2 and 3.3

3. JIRA JDO-821: "Fix sonarcloud issues of type Bugs"
https://issues.apache.org/jira/browse/JDO-821
See PR #65: https://github.com/apache/db-jdo/pull/65
<https://github.com/apache/db-jdo/pull/65>

4. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
<https://issues.apache.org/jira/browse/JDO-819>

Changes in PR#65 can be merged.
Tilmann is looking at the SonarCloud "security" issues. Seem to be innocuous.

Still more SonarCloud issues (code smell) to address. For example:
https://sonarcloud.io/project/issues?issues=AYTeBPbL_-S9Jt7nsSUW=AYTeBPbL_-S9Jt7nsSUW=db-jdo

<https://sonarcloud.io/project/issues?issues=AYTeBPbL_-S9Jt7nsSUW=AYTeBPbL_-S9Jt7nsSUW=db-jdo>

Every subclass of JDOUserException smells. Not really an issue for us.

Anyone who looks into a SonarCloud issue should add a comment to the JDO-819
JIRA with the analysis and resolution and possibly a PR. At some point we may
close the issue after the items are low enough importance.

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

6. JIRA JDO-815 "Change headers on source files to use https:// instead of
http:// " https://issues.apache.org/jira/browse/JDO-815
<https://issues.apache.org/jira/browse/JDO-815>

Ready to resolve.
AI Craig resolve it.

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

[Nov 23 2022] AI Tilmann see what else is needed to have the analysis
integrated into GitHub repo.
[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO
development and see if and how they want to be recognized on the JDO and DB web
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Re: Copyright notice is out of date

2022-12-07 Thread Craig Russell

The copyright notice is in two places:


./NOTICE:Copyright 2005-2022 The Apache Software Foundation
./tck/NOTICE.txt:Copyright 2005-2006 The Apache Software Foundation

The NOTICE.txt in tck might be historic. Do we need it?

Craig
> On Dec 6, 2022, at 17:07, Craig Russell  wrote:
> 
> I noticed this while reviewing the http https patch (hat tip Til). The 
> copyright NOTICE is out of date.
> 
> I'll write a patch which includes both the copyright notice and updated 
> instructions for release.
> 
> Craig
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Copyright notice is out of date

2022-12-06 Thread Craig Russell

I noticed this while reviewing the http https patch (hat tip Til). The 
copyright NOTICE is out of date.

I'll write a patch which includes both the copyright notice and updated 
instructions for release.

Craig

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday December 1 1100 PST 2000 CET

2022-12-01 Thread Craig Russell

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

Next meeting: Thursday December 8 1100 PST 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819

Three admins are now authorized. The main issue looks like assertions in the 
tck. The tck test methods are not recognized as tests eligible to use the 
assert statement. 

2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709
PR #60 "[JDO-709] Enable Element.TYPE for @Convert" 
https://github.com/apache/db-jdo/pull/60
PR #61 "Enable Element.TYPE for @Convert - TCK test" 
https://github.com/apache/db-jdo/pull/61 
<https://github.com/apache/db-jdo/pull/61>

Til has started writing a DataNucleus test case. Doesn't run yet. In progress. 
Nothing yet from DataNucleus.

3. JIRA JDO-815 "Change headers on source files to use https:// instead of 
http:// " https://issues.apache.org/jira/browse/JDO-815 
<https://issues.apache.org/jira/browse/JDO-815>

1659 changed files in git branch jdo-815-http-to-https

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 see what else is needed to have the analysis 
integrated into GitHub repo.
[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his advice on 
JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Wednesday November 23 noon PST 2100 CET

2022-11-23 Thread Craig Russell

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

Next meeting: Thursday December 1 1100 PST 2000 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819 
<https://issues.apache.org/jira/browse/JDO-819>

Three admins are planned for the service: mbo, clr, and til. All three have 
signed in. 
AI infra activate the process. 
AI Tilmann see what else is needed to have the analysis integrated into GitHub 
repo.

2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709
PR #60 "[JDO-709] Enable Element.TYPE for @Convert" 
https://github.com/apache/db-jdo/pull/60
PR #61 "Enable Element.TYPE for @Convert - TCK test" 
https://github.com/apache/db-jdo/pull/61

Looks like the test case should work as soon as DataNucleus is adapted.
AI Tilmann follow up with Andy/DataNucleus for his advice. It may be required 
to write a JUnit test for it.

Should we also add the "always treat this class as convertible" to the jdo 
metadata? It would require updates to the .xsd and .dtd as well.

3. JIRA JDO-815 "Change headers on source files to use https:// instead of 
http:// " https://issues.apache.org/jira/browse/JDO-815 
<https://issues.apache.org/jira/browse/JDO-815>

In progress.

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:

[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

Regards Michael


Craig L Russell
c...@apache.org

Minutes: JDO TCK Conference Call Thursday November 17 1100 PST 2000 CET

2022-11-17 Thread Craig Russell

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

Next meeting: Wednesday 1200 noon PST 2100 CET

Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819 
<https://issues.apache.org/jira/browse/JDO-819>

Tilmann raised a ticket with infra. INFRA-23891 is linked from JDO-819

2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709
PR #60 "[JDO-709] Enable Element.TYPE for @Convert" 
https://github.com/apache/db-jdo/pull/60
PR #61 "Enable Element.TYPE for @Convert - TCK test" 
https://github.com/apache/db-jdo/pull/61 
<https://github.com/apache/db-jdo/pull/61>

Questions from the PR:

• Does the converter or the convertible class need to be declared in 
one of the .jdo or .orm files?

Should not be needed.

• Do we need to initialize the ConvertiblePoint fields in 
PCRectPointTypeAnnotated?

The JDO implementation should initialize the field (creating a new instance of 
the convertible class and then setting the value) when reading from the 
database. The application should initialize the fields when creating a new 
instance.

Suggestion to improve the test case: annotate the fields individually  and see 
if the test case works. Raise an issue (feature request) with DataNucleus with 
the results.

3. JIRA JDO-815 "Change headers on source files to use https:// instead of 
http:// " https://issues.apache.org/jira/browse/JDO-815 
<https://issues.apache.org/jira/browse/JDO-815>

Still in progress. 

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:

[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case using 
annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Re: Zoom chat settings

2022-11-03 Thread Craig Russell

It was very painful but I found out how to enable the chat button during 
meetings.

> On Nov 3, 2022, at 16:21, Craig Russell  wrote:
> 
> I'm still not clear whether a chat can be tied to a zoom call or if it's 
> always in a separate window...
> 
>> On Nov 3, 2022, at 15:46, Craig Russell  wrote:
>> 
>> Instructions for chat: https://www.youtube.com/watch?v=qWWz5ZommlQ
>> 
>> Next meeting: 
>> https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09
>> 
>> Craig L Russell
>> c...@apache.org
>> 
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Re: Zoom chat settings

2022-11-03 Thread Craig Russell

I'm still not clear whether a chat can be tied to a zoom call or if it's always 
in a separate window...

> On Nov 3, 2022, at 15:46, Craig Russell  wrote:
> 
> Instructions for chat: https://www.youtube.com/watch?v=qWWz5ZommlQ
> 
> Next meeting: 
> https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Zoom chat settings

2022-11-03 Thread Craig Russell

Instructions for chat: https://www.youtube.com/watch?v=qWWz5ZommlQ

Next meeting: 
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09

Craig L Russell
c...@apache.org

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1708 matches

Mail list logo