Minutes: JDO TCK Conference Call Thursday June 8 1100 PDT 2000 CEST
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
[jira] [Updated] (JDO-827) Consider (re-)moving JNDI support
[
https://issues.apache.org/jira/browse/JDO-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-827:
-
Description:
The JDO API has two JNDI dependencies:
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context
context)}} and
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context context,
ClassLoader loader)}}
The JNDI dependency complicates building and running the TCK (because of the
non-free nature of the implementation). It is also the only part of the API
that stops it being compatible with Android. The CI runs currently have all
tests disabled that depend on JNDI (TBD, how does it compile without the
classes???).
There are many options for simplifying this issue:
* Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB, JMS.
* Move the two methods into a separate JDOJNDIHelper. This would (probably)
allow us to more easily exclude it from builds when desired, for example using
Java 9 modules.
* Provide a dummy implementation of the JNDI classes. This would allow
compiling the API without problems (also on Android), but we would still need
to exclude it from tests.
* Switch to a free leightweight implementation, e.g.
[https://github.com/h-thurow/Simple-JNDI] or
https://github.com/dattack/standalone-jndi
was:
The JDO API has two JNDI dependencies:
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context
context)}} and
{{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context context,
ClassLoader loader)}}
The JNDI dependency complicates building and running the TCK (because of the
non-free nature of the implementation). It is also the only part of the API
that stops it being compatible with Android. The CI runs currently have all
tests disabled that depend on JNDI (TBD, how does it compile without the
classes???).
There are many options for simplifying this issue:
* Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB, JMS.
* Move the two methods into a separate JDOJNDIHelper. This would (probably)
allow us to more easily exclude it from builds when desired, for example using
Java 9 modules.
* Provide a dummy implementation of the JNDI classes. This would allow
compiling the API without problems (also on Android), but we would still need
to exclude it from tests.
* Switch to a free leightweight implementation, e.g.
https://github.com/h-thurow/Simple-JNDI
> Consider (re-)moving JNDI support
> -
>
> Key: JDO-827
> URL: https://issues.apache.org/jira/browse/JDO-827
> Project: JDO
> Issue Type: Improvement
> Components: api
>Affects Versions: JDO 3.2, JDO 3.2.1
>Reporter: Tilmann Zäschke
>Priority: Major
>
> The JDO API has two JNDI dependencies:
> {{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context
> context)}} and
> {{JDOHelper.getPersistenceManagerFactory(String jndiLocation, Context
> context, ClassLoader loader)}}
> The JNDI dependency complicates building and running the TCK (because of the
> non-free nature of the implementation). It is also the only part of the API
> that stops it being compatible with Android. The CI runs currently have all
> tests disabled that depend on JNDI (TBD, how does it compile without the
> classes???).
> There are many options for simplifying this issue:
> * Drop JNDI support? Is JNDI still used? Probably yes, see JDBC, JPA, EJB,
> JMS.
> * Move the two methods into a separate JDOJNDIHelper. This would (probably)
> allow us to more easily exclude it from builds when desired, for example
> using Java 9 modules.
> * Provide a dummy implementation of the JNDI classes. This would allow
> compiling the API without problems (also on Android), but we would still need
> to exclude it from tests.
> * Switch to a free leightweight implementation, e.g.
> [https://github.com/h-thurow/Simple-JNDI] or
> https://github.com/dattack/standalone-jndi
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (JDO-828) Set up automated mail subjects for GitHub action responses
[ https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen resolved JDO-828. - Resolution: Fixed > Set up automated mail subjects for GitHub action responses > -- > > Key: JDO-828 > URL: https://issues.apache.org/jira/browse/JDO-828 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > On the general Apache community page, a range of email subjects for automated > email created for different actions on GitHub have been suggested: > [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent] > These settings should be applied to the JDO repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (JDO-828) Set up automated mail subjects for GitHub action responses
[ https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen reopened JDO-828: - > Set up automated mail subjects for GitHub action responses > -- > > Key: JDO-828 > URL: https://issues.apache.org/jira/browse/JDO-828 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > On the general Apache community page, a range of email subjects for automated > email created for different actions on GitHub have been suggested: > [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent] > These settings should be applied to the JDO repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (JDO-828) Set up automated mail subjects for GitHub action responses
[ https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bouschen closed JDO-828. --- Resolution: Fixed > Set up automated mail subjects for GitHub action responses > -- > > Key: JDO-828 > URL: https://issues.apache.org/jira/browse/JDO-828 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > On the general Apache community page, a range of email subjects for automated > email created for different actions on GitHub have been suggested: > [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent] > These settings should be applied to the JDO repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Update GitHub action versions & replace deprecated commands (db-jdo-site)
tobous merged PR #48: URL: https://github.com/apache/db-jdo-site/pull/48 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Update GitHub action versions (db-jdo)
tobous merged PR #79: URL: https://github.com/apache/db-jdo/pull/79 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [db-jdo-site] tobous merged pull request #47: JDO-828 - Add setup for subjects for automated GitHub emails
tobous merged PR #47: URL: https://github.com/apache/db-jdo-site/pull/47 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [db-jdo] tobous merged pull request #78: JDO-828 - Add setup for subjects for automated GitHub emails
tobous merged PR #78: URL: https://github.com/apache/db-jdo/pull/78 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (JDO-828) Set up automated mail subjects for GitHub action responses
[ https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-828: - Fix Version/s: JDO 3.2.2 JDO 3.3 > Set up automated mail subjects for GitHub action responses > -- > > Key: JDO-828 > URL: https://issues.apache.org/jira/browse/JDO-828 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > On the general Apache community page, a range of email subjects for automated > email created for different actions on GitHub have been suggested: > [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent] > These settings should be applied to the JDO repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-828) Set up automated mail subjects for GitHub action responses
[ https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-828: - Component/s: site and infrastructure > Set up automated mail subjects for GitHub action responses > -- > > Key: JDO-828 > URL: https://issues.apache.org/jira/browse/JDO-828 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > > On the general Apache community page, a range of email subjects for automated > email created for different actions on GitHub have been suggested: > [https://community.apache.org/contributors/mailing-lists#configuring-the-subject-lines-of-the-emails-being-sent] > These settings should be applied to the JDO repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
