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

[jira] [Closed] (JDO-826) @Convert Javadoc indicates support for @Target(ElementType.TYPE,...)

2023-04-26 Thread Jira 


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

Tilmann Zäschke closed JDO-826.
---
  Assignee: Tilmann Zäschke
Resolution: Fixed

> @Convert Javadoc indicates support for @Target(ElementType.TYPE,...)
> 
>
> Key: JDO-826
> URL: https://issues.apache.org/jira/browse/JDO-826
> Project: JDO
>  Issue Type: Bug
>  Components: api
>Affects Versions: JDO 3.2
>Reporter: Tilmann Zäschke
>Assignee: Tilmann Zäschke
>Priority: Major
> Fix For: JDO 3.2.2
>
>
> The javadoc of the @Convert annotation claims that it can be placed on types, 
> e.g.
> {code:java}
> @Convert(value = ConvertiblePointToStringConverter.class)
> public class ConvertiblePoint {
>   ...
> }
> {code}
> While this feature is desirable, there is currently no implementation of it 
> in the reference implementation.
> For now, the javadoc should be fixed by removing the section about 
> @Target(ElementType.TYPE,...).
> Once the implementation is resourced (volunteers welcome!) the section can be 
> put back in place.
>  
> Context:
>  * Original discussion: 
> [JDO-709|https://issues.apache.org/jira/browse/JDO-709], starting 2022-10-17
>  * PR by original problem reporter: [https://github.com/apache/db-jdo/pull/60]
>  * Copy of original PR with additional TCK test: 
> [https://github.com/apache/db-jdo/pull/61]
>  * Tickets with problem description on reference implementation: 
> [https://github.com/datanucleus/datanucleus-api-jdo/issues/127]



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

[GitHub] [db-jdo] tzaeschke merged pull request #76: JDO-823 - Make fields in JDOException final

2023-04-26 Thread via GitHub 


tzaeschke merged PR #76:
URL: https://github.com/apache/db-jdo/pull/76


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