[jira] [Updated] (JDO-808) Java 18

2022-03-31 Thread Jira 


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

Tilmann Zäschke updated JDO-808:

Description: 
Java 18 comes with several changes that are expected to cause warnings or other 
problems: 
[email|https://lists.apache.org/thread/3snsshz2ddb3lpzwfh03fpk05mb4b3fc]. 
Expected problems include warnings about use of the now deprecated 
SecurityManager.

A test run with OpenJDK 18 results in an error during compilation due to plugin 
incompatibility.

 

Task: Find and fix problems with JDK 18.

 

See also: https://issues.apache.org/jira/browse/DERBY-7126, 
https://issues.apache.org/jira/browse/DERBY-7137, 
https://issues.apache.org/jira/browse/DERBY-7138

  was:
Java 18 comes with several changes that are expected to cause warnings or other 
problems: 
[email|https://lists.apache.org/thread/3snsshz2ddb3lpzwfh03fpk05mb4b3fc]. 
Expected problems include warnings about use of the now deprecated 
SecurityManager.

A test run with OpenJDK 18 results in an error during compilation due to plugin 
incompatibility.

 

Task: Find and fix problems with JDK 18.

 

 


> Java 18
> ---
>
> Key: JDO-808
> URL: https://issues.apache.org/jira/browse/JDO-808
> Project: JDO
>  Issue Type: Bug
>  Components: tck
>Affects Versions: JDO 3.2
>Reporter: Tilmann Zäschke
>Assignee: Tilmann Zäschke
>Priority: Major
>
> Java 18 comes with several changes that are expected to cause warnings or 
> other problems: 
> [email|https://lists.apache.org/thread/3snsshz2ddb3lpzwfh03fpk05mb4b3fc]. 
> Expected problems include warnings about use of the now deprecated 
> SecurityManager.
> A test run with OpenJDK 18 results in an error during compilation due to 
> plugin incompatibility.
>  
> Task: Find and fix problems with JDK 18.
>  
> See also: https://issues.apache.org/jira/browse/DERBY-7126, 
> https://issues.apache.org/jira/browse/DERBY-7137, 
> https://issues.apache.org/jira/browse/DERBY-7138



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [db-jdo] tzaeschke opened a new pull request #41: Java 18 compatibility

2022-03-31 Thread GitBox 


tzaeschke opened a new pull request #41:
URL: https://github.com/apache/db-jdo/pull/41


   Investigate Java 18 compatibility. See issue 
[JDO-808](https://issues.apache.org/jira/browse/JDO-808).


-- 
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] [Commented] (JDO-808) Java 18

2022-03-31 Thread Jira 


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

Tilmann Zäschke commented on JDO-808:
-

After upgrading to `apache-25.pom` compilation reports the following warnings:
{noformat}
[WARNING] [options] bootstrap class path not set in conjunction with -source 8
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[29,20]
 [removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\I18NHelper.java:[22,20] 
[removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\identity\ObjectIdentity.java:[29,20]
 [removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\JDOHelper.java:[35,20] 
[removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[211,8]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[211,36]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[457,8]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[457,36]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[494,8]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[494,36]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[578,8]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[578,35]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[600,8]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[600,35]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[683,14]
 [removal] SecurityManager in java.lang has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[683,42]
 [removal] getSecurityManager() in System has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[781,32]
 [removal] Integer(int) in Integer has been deprecated and marked for removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\JDOImplHelper.java:[882,17]
 [removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\I18NHelper.java:[110,34] 
[removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\I18NHelper.java:[357,25] 
[removal] Integer(int) in Integer has been deprecated and marked for removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\spi\I18NHelper.java:[392,15] 
[removal] AccessController in java.security has been deprecated and marked for 
removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\PersistenceManager.java:[566,36]
 [unchecked] Possible heap pollution from parameterized vararg type T
  where T is a type-variable:
    T extends Object declared in method makePersistentAll(T...)
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\PersistenceManager.java:[1096,32]
 [unchecked] Possible heap pollution from parameterized vararg type T
  where T is a type-variable:
    T extends Object declared in method detachCopyAll(T...)
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\identity\IntIdentity.java:[131,15]
 [removal] Integer(int) in Integer has been deprecated and marked for removal
[WARNING] 
C:\work\github\db-jdo\api\src\main\java\javax\jdo\identity\CharIdentity.java:[142,15]
 [removal] Character(char) in Character has been deprecated and marked for 
removal

[jira] [Created] (JDO-808) Java 18

2022-03-31 Thread Jira 
Tilmann Zäschke created JDO-808:
---

 Summary: Java 18
 Key: JDO-808
 URL: https://issues.apache.org/jira/browse/JDO-808
 Project: JDO
  Issue Type: Bug
  Components: tck
Affects Versions: JDO 3.2
Reporter: Tilmann Zäschke
Assignee: Tilmann Zäschke


Java 18 comes with several changes that are expected to cause warnings or other 
problems: 
[email|https://lists.apache.org/thread/3snsshz2ddb3lpzwfh03fpk05mb4b3fc]. 
Expected problems include warnings about use of the now deprecated 
SecurityManager.

A test run with OpenJDK 18 results in an error during compilation due to plugin 
incompatibility.

 

Task: Find and fix problems with JDK 18.

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Minutes: JDO TCK Conference Call Thursday March 31 11 PM PDT 20 CEST

2022-03-31 Thread Craig Russell 
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell

Next meeting: Thursday 11:00 PDT 20:00 CEST

Agenda:
1. New PR #40 "Use apache URL for schemaLocation of JDO XSDs and DTDs" 
https://github.com/apache/db-jdo/pull/40 
   

JDO-806 "Use apache URL for schemaLocation of JDO XSDs" 
https://issues.apache.org/jira/browse/JDO-806
   Question: name of the jdo namespace, see JIRA comment from Andy

AI Michael send message to d...@geronimo.apache.org to see if they have any 
suggestions or implement Andy's comment.

2. JDK 18 General Availability, and oracle-actions/setup-java see email from 
Craig

The impact on JDO is that we use the security manager which is deprecated in 
JDK 18 and removed in JDK 19.
For the record from Andy:

Not that it directly impacts on Apache JDO building, but DataNucleus v6.0 
currently works for JDKs 8 through 17. This range is limited by the internal 
repackaged version of the ASM bytecode library used (currently using v9.1). 
There is a v9.2 available that adds support for JDK 18, but since this JDK is 
not an LTS release I'm not contemplating it anytime soon; maybe when there is 
a version of ASM for JDK 19.

Therefore, JDO have no plans to support JDK 18 soon, and will support JDK 19 
when we can.

AI Tilmann: create a JDO JIRA to remove the security manager from the code and 
make any other changes needed for JDK 18/19.

3. TCK : TreeSetCollections CHALLENGE see email from Andy

AI Andy: please file a JDO JIRA to continue the discussion. Perhaps suggest 
changes to the ORM files?

4. JIRA JDO-805 "Consolidate download pages" 
https://issues.apache.org/jira/browse/JDO-805
5. Other issues

Action Items from weeks past:

[Feb 17 2022] AI everyone JDO-805 take a look and comment on the proposal.
[Jan 27 2022] AI Craig update the instructions in the 3.2  branch and create a 
new PR for the changes. This will include putting the proposed release into the 
dev directory before the vote.
[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: TCK : TreeSetCollections CHALLENGE

2022-03-31 Thread Andy Jefferson 
> Upon inspection of the TCK orm.xml files I find the embedded fields such as
> TreeSetCollections.TreeSetOfObject1 are supposed to be embedded in a join
> table, yet have no  block, though they do for the other java.util
> type tests.

FWIW The same comment applies to the ORM files for ArrayList (app id and ds 
id). List, LinkedList, Vector all have the  block, whereas ArrayList 
doesn't. 

The requisite schema for ArrayList and TreeSet likewise don't have the 
embedded columns needed, so that would need updating too.
Currently, for those cases, it seems to be simply ignoring the embedded flag 
and storing the SimpleClass in its own table with FK across to it from the 
join table.



-- 
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)

Re: JDO TCK Conference Call Thursday March 31 11 PM PDT 20 CEST

2022-03-31 Thread Andy Jefferson 
> 2. JDK 18 General Availability, and oracle-actions/setup-java see email

Not that it directly impacts on Apache JDO building, but DataNucleus v6.0 
currently works for JDKs 8 through 17. This range is limited by the internal 
repackaged version of the ASM bytecode library used (currently using v9.1). 
There is a v9.2 available that adds support for JDK 18, but since this JDK is 
not an LTS release I'm not contemplating it anytime soon; maybe when there is 
a version of ASM for JDK 19.


Regards
-- 
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)