A little help with git messages
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
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
[jira] [Resolved] (JDO-832) Remove RunTCK option jdo.tck.skipJndi
[ https://issues.apache.org/jira/browse/JDO-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-832. -- Resolution: Fixed > Remove RunTCK option jdo.tck.skipJndi > - > > Key: JDO-832 > URL: https://issues.apache.org/jira/browse/JDO-832 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > With JDO-827 the TCK comes with its own JNDI mock implementation. > Without an JNDI implemention we needed to skip the JNDI TCK test cases when > running the tck from an automatic build. This is not necessary anymore, so we > do not need the option jdo.tck.skipJndi anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] JDO-832: Remove RunTCK option jdo.tck.skipJndi (db-jdo)
mboapache merged PR #82: URL: https://github.com/apache/db-jdo/pull/82 -- 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] [Resolved] (JDO-827) Consider (re-)moving JNDI support
[
https://issues.apache.org/jira/browse/JDO-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilmann Zäschke resolved JDO-827.
-
Fix Version/s: JDO 3.2.2
JDO 3.3
Assignee: Tilmann Zäschke
Resolution: Fixed
> 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
>Assignee: Tilmann Zäschke
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> 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)
