[jira] [Updated] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-840: - Fix Version/s: (was: JDO 3.2.2) > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen closed JDO-840. > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-840. -- Resolution: Fixed > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-840) Fix changes links on JDO news site
Michael Bouschen created JDO-840: Summary: Fix changes links on JDO news site Key: JDO-840 URL: https://issues.apache.org/jira/browse/JDO-840 Project: JDO Issue Type: Improvement Components: site and infrastructure Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The current JDO site lists the JDO release on the start page. For each release there is a link to the Jira version listing all the changes for the particular release. For the releases older than JDO 3.2 you must be logged in into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 this is not necessary. * Change the link for the older release such that it is not necessary to be logged into Jira to see the list. * Releases older than 3.2 may not be downloaded anymore, so th etext "You can download the release from ..." is misleading and shoudl be skipped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-840: Assignee: Michael Bouschen > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-840: - Fix Version/s: JDO 3.2.2 > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JDO-836) TCK: QueryCancel Test class fails
[ https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823326#comment-17823326 ] Michael Bouschen commented on JDO-836: -- New branch JDO-836: * Added cancel.conf configuration file * Added log Statements in QueryCancel TCK class * Disabled second test method in QueryCancel to avaoid parallel threads > TCK: QueryCancel Test class fails > - > > Key: JDO-836 > URL: https://issues.apache.org/jira/browse/JDO-836 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Attachments: cancel.conf > > > The TCK test class QueryCancel fails. It is not part of any test > configuration so it is never executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails
[
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
]
Michael Bouschen edited comment on JDO-836 at 2/27/24 7:20 PM:
---
I added some log statements 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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to tck/src/main/resources/conf {{and}}
call mvn -Djdo.tck.cfglist=cancel.conf clean install in the tck subdirectory.
was (Author: mbo):
I added some log statements 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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to tck/src/main/resources/conf {{and}}
call mvn -Djdo.tck.cfglist=cancel.conf clean install
> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
> Issue Type: Task
> Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test
> configuration so it is never executed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails
[
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
]
Michael Bouschen edited comment on JDO-836 at 2/27/24 7:19 PM:
---
I added some log statements 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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to tck/src/main/resources/conf {{and}}
call mvn -Djdo.tck.cfglist=cancel.conf clean install
was (Author: mbo):
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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to tck/src/main/resources/conf {{and}}
call mvn -Djdo.tck.cfglist=cancel.conf clean install
> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
> Issue Type: Task
> Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test
> configuration so it is never executed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JDO-836) TCK: QueryCancel Test class fails
[
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
]
Michael Bouschen edited comment on JDO-836 at 2/27/24 7:18 PM:
---
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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to tck/src/main/resources/conf {{and}}
call mvn -Djdo.tck.cfglist=cancel.conf clean install
was (Author: mbo):
I added some lof statement to check thta 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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to {{tck/src/main/resources/conf }}and call {{mvn
-Djdo.tck.cfglist=cancel.conf clean install}}
> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
> Issue Type: Task
> Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test
> configuration so it is never executed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JDO-836) TCK: QueryCancel Test class fails
[
https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820861#comment-17820861
]
Michael Bouschen commented on JDO-836:
--
I added some lof statement to check thta 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 execute
1708809300860
22:15:00,861 (Query Executor) INFO [org.apache.jdo.tck] - query execute took
49823ms
You can use the attched configuration cancel.conf to run the QueryCancel TCK
test.
Copy the file cancel.conf to {{tck/src/main/resources/conf }}and call {{mvn
-Djdo.tck.cfglist=cancel.conf clean install}}
> TCK: QueryCancel Test class fails
> -
>
> Key: JDO-836
> URL: https://issues.apache.org/jira/browse/JDO-836
> Project: JDO
> Issue Type: Task
> Components: tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Attachments: cancel.conf
>
>
> The TCK test class QueryCancel fails. It is not part of any test
> configuration so it is never executed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JDO-836) TCK: QueryCancel Test class fails
[ https://issues.apache.org/jira/browse/JDO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-836: - Attachment: cancel.conf > TCK: QueryCancel Test class fails > - > > Key: JDO-836 > URL: https://issues.apache.org/jira/browse/JDO-836 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Attachments: cancel.conf > > > The TCK test class QueryCancel fails. It is not part of any test > configuration so it is never executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-831) tck: improve tck tests for performance
[ https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-831. -- Resolution: Fixed TCK query test cases have been optimzed. > tck: improve tck tests for performance > -- > > Key: JDO-831 > URL: https://issues.apache.org/jira/browse/JDO-831 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The performance of the tck test suite might be improved by using: > * multi-threading > * parallel execution of tests that do not change the database > * setup/teardown optimization for tests that do not change the database -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution
[ https://issues.apache.org/jira/browse/JDO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809131#comment-17809131 ] Michael Bouschen commented on JDO-837: -- The flag jdo.tck.parallel.execution ist added to the branch JDO-831 > TCK: add a JDO flag to enable/disable parallel execution > > > Key: JDO-837 > URL: https://issues.apache.org/jira/browse/JDO-837 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > Add a flag to RunTCK to enable/disable parallel execution of the test methods > in TCK test classes: > jdo.tck.parallel.execution=false|true default true > The flag is used to set the flag junit.jupiter.execution.parallel.enabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution
Michael Bouschen created JDO-837: Summary: TCK: add a JDO flag to enable/disable parallel execution Key: JDO-837 URL: https://issues.apache.org/jira/browse/JDO-837 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen Add a flag to RunTCK to enable/disable parallel execution of the test methods in TCK test classes: jdo.tck.parallel.execution=false|true default true The flag is used to set the flag junit.jupiter.execution.parallel.enabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-837) TCK: add a JDO flag to enable/disable parallel execution
[ https://issues.apache.org/jira/browse/JDO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-837: Assignee: Michael Bouschen > TCK: add a JDO flag to enable/disable parallel execution > > > Key: JDO-837 > URL: https://issues.apache.org/jira/browse/JDO-837 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > Add a flag to RunTCK to enable/disable parallel execution of the test methods > in TCK test classes: > jdo.tck.parallel.execution=false|true default true > The flag is used to set the flag junit.jupiter.execution.parallel.enabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-836) TCK: QueryCancel Test class fails
Michael Bouschen created JDO-836: Summary: TCK: QueryCancel Test class fails Key: JDO-836 URL: https://issues.apache.org/jira/browse/JDO-836 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The TCK test class QueryCancel fails. It is not part of any test configuration so it is never executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-835) TCK: Check ResultClassRequirementsMap when running multithreaded
Michael Bouschen created JDO-835: Summary: TCK: Check ResultClassRequirementsMap when running multithreaded Key: JDO-835 URL: https://issues.apache.org/jira/browse/JDO-835 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The test cases of ResultClassRequirementsMap return wrong results when running multithreaded, see source code for details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-830. -- Resolution: Fixed > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > 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.3 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-830: - Fix Version/s: (was: JDO 3.2.2) > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > 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.3 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781491#comment-17781491 ] Michael Bouschen commented on JDO-830: -- First version of JUnit 5 migration: https://github.com/apache/db-jdo/tree/JDO-830 > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > 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 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-822) Verify compatibility with JDK 21
[ https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-822: - Description: JDK 21 reached [General Availability|https://openjdk.org/projects/jdk8/milestones#General_Availability] on 19 September 2023, so we should go for JDK 21 instaed of JDK 20. Summary: Verify compatibility with JDK 21 (was: Verify compatibility with JDK 20) > Verify compatibility with JDK 21 > > > Key: JDO-822 > URL: https://issues.apache.org/jira/browse/JDO-822 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Priority: Major > > JDK 21 reached [General > Availability|https://openjdk.org/projects/jdk8/milestones#General_Availability] > on 19 September 2023, so we should go for JDK 21 instaed of JDK 20. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-830: Assignee: Michael Bouschen > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > 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 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-833) Use automated release infra for JDO releases
[ https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-833: - Description: Signing releases using automated release infra is a possibility for us to use for the next release. See https://infra.apache.org/release-signing.html#automated-release-signing was:Signing releases using automated release infra is a possibility for us to use for the next release. > Use automated release infra for JDO releases > > > Key: JDO-833 > URL: https://issues.apache.org/jira/browse/JDO-833 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > Signing releases using automated release infra is a possibility for us to use > for the next release. > See https://infra.apache.org/release-signing.html#automated-release-signing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-833) Use automated release infra for JDO releases
Michael Bouschen created JDO-833: Summary: Use automated release infra for JDO releases Key: JDO-833 URL: https://issues.apache.org/jira/browse/JDO-833 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen Signing releases using automated release infra is a possibility for us to use for the next release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-833) Use automated release infra for JDO releases
[ https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-833: - Fix Version/s: JDO 3.2.2 JDO 3.3 > Use automated release infra for JDO releases > > > Key: JDO-833 > URL: https://issues.apache.org/jira/browse/JDO-833 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > Signing releases using automated release infra is a possibility for us to use > for the next release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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)
[jira] [Created] (JDO-832) Remove RunTCK option jdo.tck.skipJndi
Michael Bouschen created JDO-832: Summary: 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 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)
[jira] [Resolved] (JDO-829) api: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-829. -- Resolution: Fixed > api: Migrate JUnit tests to version 5 > - > > Key: JDO-829 > URL: https://issues.apache.org/jira/browse/JDO-829 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The unit tests in the api subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * https://www.baeldung.com/junit-5-migration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-830) tck: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-830: - Description: The tck tests in the tck subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. Links: * [https://junit.org/junit5/docs/current/user-guide/] * [https://www.baeldung.com/junit-5] * [https://www.baeldung.com/junit-5-migration] * [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] was: The tck tests in the tck subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. Links: * [https://junit.org/junit5/docs/current/user-guide/] * [https://www.baeldung.com/junit-5] * https://www.baeldung.com/junit-5-migration > tck: Migrate JUnit tests to version 5 > - > > Key: JDO-830 > URL: https://issues.apache.org/jira/browse/JDO-830 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The tck tests in the tck subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * [https://www.baeldung.com/junit-5-migration] > * > [https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-831) tck: improve tck tests for performance
[ https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-831: - Description: The performance of the tck test suite might be improved by using: * multi-threading * parallel execution of tests that do not change the database * setup/teardown optimization for tests that do not change the database was: The performance of the tck test suite might be improved by using: * multi-threading * parallel execution of tests that do not change the database * setup/teardown optimization for tests that do not change the database https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build > tck: improve tck tests for performance > -- > > Key: JDO-831 > URL: https://issues.apache.org/jira/browse/JDO-831 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The performance of the tck test suite might be improved by using: > * multi-threading > * parallel execution of tests that do not change the database > * setup/teardown optimization for tests that do not change the database -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-831) tck: improve tck tests for performance
[ https://issues.apache.org/jira/browse/JDO-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-831: - Fix Version/s: JDO 3.2.2 JDO 3.3 > tck: improve tck tests for performance > -- > > Key: JDO-831 > URL: https://issues.apache.org/jira/browse/JDO-831 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The performance of the tck test suite might be improved by using: > * multi-threading > * parallel execution of tests that do not change the database > * setup/teardown optimization for tests that do not change the database > https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-831) tck: improve tck tests for performance
Michael Bouschen created JDO-831: Summary: tck: improve tck tests for performance Key: JDO-831 URL: https://issues.apache.org/jira/browse/JDO-831 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The performance of the tck test suite might be improved by using: * multi-threading * parallel execution of tests that do not change the database * setup/teardown optimization for tests that do not change the database https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-830) tck: Migrate JUnit tests to version 5
Michael Bouschen created JDO-830: Summary: tck: Migrate JUnit tests to version 5 Key: JDO-830 URL: https://issues.apache.org/jira/browse/JDO-830 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen Fix For: JDO 3.2.2, JDO 3.3 The tck tests in the tck subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. Links: * [https://junit.org/junit5/docs/current/user-guide/] * [https://www.baeldung.com/junit-5] * https://www.baeldung.com/junit-5-migration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-829) api: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-829: - Description: The unit tests in the api subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. Links: * [https://junit.org/junit5/docs/current/user-guide/] * [https://www.baeldung.com/junit-5] * https://www.baeldung.com/junit-5-migration was:The unit tests in the api subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > api: Migrate JUnit tests to version 5 > - > > Key: JDO-829 > URL: https://issues.apache.org/jira/browse/JDO-829 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The unit tests in the api subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. > Links: > * [https://junit.org/junit5/docs/current/user-guide/] > * [https://www.baeldung.com/junit-5] > * https://www.baeldung.com/junit-5-migration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-829) api: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-829: Assignee: Michael Bouschen > api: Migrate JUnit tests to version 5 > - > > Key: JDO-829 > URL: https://issues.apache.org/jira/browse/JDO-829 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The unit tests in the api subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-829) api: Migrate JUnit tests to version 5
[ https://issues.apache.org/jira/browse/JDO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-829: - Fix Version/s: JDO 3.2.2 JDO 3.3 > api: Migrate JUnit tests to version 5 > - > > Key: JDO-829 > URL: https://issues.apache.org/jira/browse/JDO-829 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The unit tests in the api subproject are using JUnit 4 and are written in a > JUnit 3.8.1 style. The tests should be migrated to JUnit 5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-829) api: Migrate JUnit tests to version 5
Michael Bouschen created JDO-829: Summary: api: Migrate JUnit tests to version 5 Key: JDO-829 URL: https://issues.apache.org/jira/browse/JDO-829 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The unit tests in the api subproject are using JUnit 4 and are written in a JUnit 3.8.1 style. The tests should be migrated to JUnit 5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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] [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)
[jira] [Created] (JDO-825) Improve exectck classes
Michael Bouschen created JDO-825: Summary: Improve exectck classes Key: JDO-825 URL: https://issues.apache.org/jira/browse/JDO-825 Project: JDO Issue Type: Task Components: tck Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen Some exectck classes may be improved: * AbstractTCKMojo, PropertyUtils, Utilites: close reader or stream in a try-with-resource * PropertyUtils: remove unused methods * AbstractTCKMojo, Enhance, RunTCK: Replace the type specification in the constructoir call with the diamond operator (<>) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-825) Improve exectck classes
[ https://issues.apache.org/jira/browse/JDO-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-825: Assignee: Michael Bouschen > Improve exectck classes > --- > > Key: JDO-825 > URL: https://issues.apache.org/jira/browse/JDO-825 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > Some exectck classes may be improved: > * AbstractTCKMojo, PropertyUtils, Utilites: close reader or stream in a > try-with-resource > * PropertyUtils: remove unused methods > * AbstractTCKMojo, Enhance, RunTCK: Replace the type specification in the > constructoir call with the diamond operator (<>) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-823) Fix sonarcloud issues of type Code Smells
[ https://issues.apache.org/jira/browse/JDO-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-823: - Fix Version/s: JDO 3.3 > Fix sonarcloud issues of type Code Smells > - > > Key: JDO-823 > URL: https://issues.apache.org/jira/browse/JDO-823 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonalcloud run lists 311 issues in the category Maintainability > (Code Smells). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-823) Fix sonarcloud issues of type Code Smells
Michael Bouschen created JDO-823: Summary: Fix sonarcloud issues of type Code Smells Key: JDO-823 URL: https://issues.apache.org/jira/browse/JDO-823 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The latest sonalcloud run lists 311 issues in the category Maintainability (Code Smells). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-821) Fix sonarcloud issues of type Bugs and Security Hotspots
[ https://issues.apache.org/jira/browse/JDO-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-821. -- Resolution: Fixed The issues in the categories Reliability (= Bugs) and Security Review (= Security Hotspots) are fixed now. > Fix sonarcloud issues of type Bugs and Security Hotspots > > > Key: JDO-821 > URL: https://issues.apache.org/jira/browse/JDO-821 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-821) Fix sonarcloud issues of type Bugs and Security Hotspots
[ https://issues.apache.org/jira/browse/JDO-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-821: - Summary: Fix sonarcloud issues of type Bugs and Security Hotspots (was: Fix sonarcloud issues of type Bugs) > Fix sonarcloud issues of type Bugs and Security Hotspots > > > Key: JDO-821 > URL: https://issues.apache.org/jira/browse/JDO-821 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JDO-821) Fix sonarcloud issues of type Bugs
[ https://issues.apache.org/jira/browse/JDO-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652249#comment-17652249 ] Michael Bouschen commented on JDO-821: -- Fixed 18 issues in the category Reliability marked as Bugs * JDOException: javadoc sentence was flagged as code in comments because of an semikolon. * JDOException: Redefined method missed a synchronized keyxword * JDOException: printStackTrace removed synchronized method qualifier, because method body is already synchronized. * package.html: missing doctype in javadoc * package.html: missing language spec in html element of javadoc * package.html: replaced by * SingleFieldIdentity: added synchronized keyword to setter because corresponding getter was already synchronized * Adapted jdo-signature.txt because of the above synchronized changes. > Fix sonarcloud issues of type Bugs > -- > > Key: JDO-821 > URL: https://issues.apache.org/jira/browse/JDO-821 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-819) Code quality analysis
[ https://issues.apache.org/jira/browse/JDO-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-819: - Description: Many Apache projects analyze code health: [https://sonarcloud.io/organizations/apache/projects] Maybe we should do the same for JDO? Here is the sonarcloud link for db-jdo: https://sonarcloud.io/summary/overall?id=db-jdo was: Many Apache projects analyze code health: [https://sonarcloud.io/organizations/apache/projects|https://sonarcloud.io/organizations/apache/projects] Maybe we should do the same for JDO? > Code quality analysis > - > > Key: JDO-819 > URL: https://issues.apache.org/jira/browse/JDO-819 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Reporter: Tilmann Zäschke >Priority: Minor > > Many Apache projects analyze code health: > [https://sonarcloud.io/organizations/apache/projects] > Maybe we should do the same for JDO? > Here is the sonarcloud link for db-jdo: > https://sonarcloud.io/summary/overall?id=db-jdo > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-820) Clean up copyright NOTICE and references
[ https://issues.apache.org/jira/browse/JDO-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-820. -- Resolution: Fixed > Clean up copyright NOTICE and references > > > Key: JDO-820 > URL: https://issues.apache.org/jira/browse/JDO-820 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Assignee: Tilmann Zäschke >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > Remove copyright notice from tck and remove copyright references from source > files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-820) Clean up copyright NOTICE and references
[ https://issues.apache.org/jira/browse/JDO-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-820: - Fix Version/s: JDO 3.2.2 JDO 3.3 > Clean up copyright NOTICE and references > > > Key: JDO-820 > URL: https://issues.apache.org/jira/browse/JDO-820 > Project: JDO > Issue Type: Task > Components: tck >Affects Versions: JDO 3.2.1 >Reporter: Tilmann Zäschke >Assignee: Tilmann Zäschke >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > Remove copyright notice from tck and remove copyright references from source > files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-821) Fix sonarcloud issues of type Bugs
[ https://issues.apache.org/jira/browse/JDO-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-821: - Fix Version/s: JDO 3.3 > Fix sonarcloud issues of type Bugs > -- > > Key: JDO-821 > URL: https://issues.apache.org/jira/browse/JDO-821 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-821) Fix sonarcloud issues of type Bugs
[ https://issues.apache.org/jira/browse/JDO-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-821: Assignee: Michael Bouschen > Fix sonarcloud issues of type Bugs > -- > > Key: JDO-821 > URL: https://issues.apache.org/jira/browse/JDO-821 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JDO-821) Fix sonarcloud issues of type Bugs
Michael Bouschen created JDO-821: Summary: Fix sonarcloud issues of type Bugs Key: JDO-821 URL: https://issues.apache.org/jira/browse/JDO-821 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The latest sonarcloud run lists 20 bugs in the category Reliability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-818) Use Google Java Style as the code format conventions for the JDO project
[ https://issues.apache.org/jira/browse/JDO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-818: - Affects Version/s: JDO 3.2.1 > Use Google Java Style as the code format conventions for the JDO project > > > Key: JDO-818 > URL: https://issues.apache.org/jira/browse/JDO-818 > Project: JDO > Issue Type: Task >Affects Versions: JDO 3.2.1 >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > h4. Google Java Style > I would propose moving to Google Java Style > ([https://google.github.io/styleguide/javaguide.html]) as the code formatting > style for the JDO project. > In my opinion, it offers a sensible and compact code style that is easy to > read. An overview of the rules of this style is given in the link posted > above. > h4. Google Java Format as the formatting tool > Additionally, I would propose moving to using the Google Java Format > ([https://github.com/google/google-java-format]) tool to do the formatting. > It is an open source formatter provided by Google. It is available as a > standalone JAR as well as plugin for IntelliJ and Eclipse (the Eclipse plugin > might not be as well maintained as the IntelliJ plugin). As such, the code > can be formatted using the CLI or the formatter can be integrated into the > default formatting tools of IntelliJ/Eclipse. > One big point of contention of the Google Java Formatter plugin is that it > offers very limited room for customization in order to ensure that it always > results in a uniform code formatting for all users. This is also explained in > the FAQ of the project: > [https://github.com/google/google-java-format/wiki/FAQ#i-just-need-to-configure-it-a-bit-differently-how] > h4. Possible automated integration > As Google Java Format is available as a CLI tool, it can be used as part of > the CI. For example, we could set up a Github Action that automatically > checks the formatting of newly created code and report back if it does not > match the Google Java Format style. It would also be possible to create a CI > job that automatically formats checked-in code, but I am not a big fan of > this approach as it changes code without any oversight, possibly leading to > unwanted changes (e.g. if there is a bug in the formatter logic). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-818) Use Google Java Style as the code format conventions for the JDO project
[ https://issues.apache.org/jira/browse/JDO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-818: - Component/s: api tck > Use Google Java Style as the code format conventions for the JDO project > > > Key: JDO-818 > URL: https://issues.apache.org/jira/browse/JDO-818 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > h4. Google Java Style > I would propose moving to Google Java Style > ([https://google.github.io/styleguide/javaguide.html]) as the code formatting > style for the JDO project. > In my opinion, it offers a sensible and compact code style that is easy to > read. An overview of the rules of this style is given in the link posted > above. > h4. Google Java Format as the formatting tool > Additionally, I would propose moving to using the Google Java Format > ([https://github.com/google/google-java-format]) tool to do the formatting. > It is an open source formatter provided by Google. It is available as a > standalone JAR as well as plugin for IntelliJ and Eclipse (the Eclipse plugin > might not be as well maintained as the IntelliJ plugin). As such, the code > can be formatted using the CLI or the formatter can be integrated into the > default formatting tools of IntelliJ/Eclipse. > One big point of contention of the Google Java Formatter plugin is that it > offers very limited room for customization in order to ensure that it always > results in a uniform code formatting for all users. This is also explained in > the FAQ of the project: > [https://github.com/google/google-java-format/wiki/FAQ#i-just-need-to-configure-it-a-bit-differently-how] > h4. Possible automated integration > As Google Java Format is available as a CLI tool, it can be used as part of > the CI. For example, we could set up a Github Action that automatically > checks the formatting of newly created code and report back if it does not > match the Google Java Format style. It would also be possible to create a CI > job that automatically formats checked-in code, but I am not a big fan of > this approach as it changes code without any oversight, possibly leading to > unwanted changes (e.g. if there is a bug in the formatter logic). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-818) Use Google Java Style as the code format conventions for the JDO project
[ https://issues.apache.org/jira/browse/JDO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-818: Assignee: Tobias Bouschen > Use Google Java Style as the code format conventions for the JDO project > > > Key: JDO-818 > URL: https://issues.apache.org/jira/browse/JDO-818 > Project: JDO > Issue Type: Task >Reporter: Tobias Bouschen >Assignee: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > h4. Google Java Style > I would propose moving to Google Java Style > ([https://google.github.io/styleguide/javaguide.html]) as the code formatting > style for the JDO project. > In my opinion, it offers a sensible and compact code style that is easy to > read. An overview of the rules of this style is given in the link posted > above. > h4. Google Java Format as the formatting tool > Additionally, I would propose moving to using the Google Java Format > ([https://github.com/google/google-java-format]) tool to do the formatting. > It is an open source formatter provided by Google. It is available as a > standalone JAR as well as plugin for IntelliJ and Eclipse (the Eclipse plugin > might not be as well maintained as the IntelliJ plugin). As such, the code > can be formatted using the CLI or the formatter can be integrated into the > default formatting tools of IntelliJ/Eclipse. > One big point of contention of the Google Java Formatter plugin is that it > offers very limited room for customization in order to ensure that it always > results in a uniform code formatting for all users. This is also explained in > the FAQ of the project: > [https://github.com/google/google-java-format/wiki/FAQ#i-just-need-to-configure-it-a-bit-differently-how] > h4. Possible automated integration > As Google Java Format is available as a CLI tool, it can be used as part of > the CI. For example, we could set up a Github Action that automatically > checks the formatting of newly created code and report back if it does not > match the Google Java Format style. It would also be possible to create a CI > job that automatically formats checked-in code, but I am not a big fan of > this approach as it changes code without any oversight, possibly leading to > unwanted changes (e.g. if there is a bug in the formatter logic). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (JDO-815) Change headers on source files to use https:// instead of http://
[ https://issues.apache.org/jira/browse/JDO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reopened JDO-815: -- There are still some files left to be converted. > Change headers on source files to use https:// instead of http:// > - > > Key: JDO-815 > URL: https://issues.apache.org/jira/browse/JDO-815 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Craig L Russell >Assignee: Craig L Russell >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > The license headers in all source files use > [http://www.apache.org/licenses/LICENSE-2.0] > The headers should instead use > [https://www.apache.org/licenses/LICENSE-2.0] > This change should also be made in pom.xml > We will need to wait until RAT 0.14 is released in order to pass the RAT test > for license headers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-818) Use Google Java Style as the code format conventions for the JDO project
[ https://issues.apache.org/jira/browse/JDO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-818: - Fix Version/s: JDO 3.2.2 JDO 3.3 > Use Google Java Style as the code format conventions for the JDO project > > > Key: JDO-818 > URL: https://issues.apache.org/jira/browse/JDO-818 > Project: JDO > Issue Type: Task >Reporter: Tobias Bouschen >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > h4. Google Java Style > I would propose moving to Google Java Style > ([https://google.github.io/styleguide/javaguide.html]) as the code formatting > style for the JDO project. > In my opinion, it offers a sensible and compact code style that is easy to > read. An overview of the rules of this style is given in the link posted > above. > h4. Google Java Format as the formatting tool > Additionally, I would propose moving to using the Google Java Format > ([https://github.com/google/google-java-format]) tool to do the formatting. > It is an open source formatter provided by Google. It is available as a > standalone JAR as well as plugin for IntelliJ and Eclipse (the Eclipse plugin > might not be as well maintained as the IntelliJ plugin). As such, the code > can be formatted using the CLI or the formatter can be integrated into the > default formatting tools of IntelliJ/Eclipse. > One big point of contention of the Google Java Formatter plugin is that it > offers very limited room for customization in order to ensure that it always > results in a uniform code formatting for all users. This is also explained in > the FAQ of the project: > [https://github.com/google/google-java-format/wiki/FAQ#i-just-need-to-configure-it-a-bit-differently-how] > h4. Possible automated integration > As Google Java Format is available as a CLI tool, it can be used as part of > the CI. For example, we could set up a Github Action that automatically > checks the formatting of newly created code and report back if it does not > match the Google Java Format style. It would also be possible to create a CI > job that automatically formats checked-in code, but I am not a big fan of > this approach as it changes code without any oversight, possibly leading to > unwanted changes (e.g. if there is a bug in the formatter logic). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JDO-817) Check Compiler warnings
[
https://issues.apache.org/jira/browse/JDO-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen resolved JDO-817.
--
Resolution: Fixed
> Check Compiler warnings
> ---
>
> Key: JDO-817
> URL: https://issues.apache.org/jira/browse/JDO-817
> Project: JDO
> Issue Type: Task
> Components: api, tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> There are tons of warnungs when running the compiler in the tck with
> -Xlint:unchecked. We should fix at least some of them.
> {{}}
> {{ org.apache.maven.plugins}}
> {{ maven-compiler-plugin}}
> {{ }}
> {{ true}}
> {{ true}}
> {{ -Xlint:unchecked}}
> {{ }}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JDO-815) Change headers on source files to use https:// instead of http://
[ https://issues.apache.org/jira/browse/JDO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-815: - Fix Version/s: JDO 3.3 > Change headers on source files to use https:// instead of http:// > - > > Key: JDO-815 > URL: https://issues.apache.org/jira/browse/JDO-815 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2.1 >Reporter: Craig L Russell >Assignee: Craig L Russell >Priority: Minor > Fix For: JDO 3.2.2, JDO 3.3 > > > The license headers in all source files use > [http://www.apache.org/licenses/LICENSE-2.0] > The headers should instead use > [https://www.apache.org/licenses/LICENSE-2.0] > This change should also be made in pom.xml > We will need to wait until RAT 0.14 is released in order to pass the RAT test > for license headers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-817) Check Compiler warnings
[
https://issues.apache.org/jira/browse/JDO-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-817:
-
Fix Version/s: JDO 3.3
> Check Compiler warnings
> ---
>
> Key: JDO-817
> URL: https://issues.apache.org/jira/browse/JDO-817
> Project: JDO
> Issue Type: Task
> Components: api, tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> There are tons of warnungs when running the compiler in the tck with
> -Xlint:unchecked. We should fix at least some of them.
> {{}}
> {{ org.apache.maven.plugins}}
> {{ maven-compiler-plugin}}
> {{ }}
> {{ true}}
> {{ true}}
> {{ -Xlint:unchecked}}
> {{ }}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JDO-814) Remove ant dependency
[ https://issues.apache.org/jira/browse/JDO-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-814: - Fix Version/s: JDO 3.3 > Remove ant dependency > -- > > Key: JDO-814 > URL: https://issues.apache.org/jira/browse/JDO-814 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > The api subproject has a dependency to org.apache.ant.ant and it looks like > that this is not needed anymore, so we should remove this dependency. > We shoud check whether this dependency is used in another JDO submodule. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JDO-799) Update the jdo pom with developers
[ https://issues.apache.org/jira/browse/JDO-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-799: - Fix Version/s: JDO 3.3 > Update the jdo pom with developers > -- > > Key: JDO-799 > URL: https://issues.apache.org/jira/browse/JDO-799 > Project: JDO > Issue Type: Improvement > Components: api, site and infrastructure, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2, JDO 3.3 > > > Update the developers list in the pom.xml in the parent-pom module. > Update the comitters list in team-list.adoc. > Both lists should in in sync. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JDO-817) Check Compiler warnings
[
https://issues.apache.org/jira/browse/JDO-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen reassigned JDO-817:
Assignee: Michael Bouschen
> Check Compiler warnings
> ---
>
> Key: JDO-817
> URL: https://issues.apache.org/jira/browse/JDO-817
> Project: JDO
> Issue Type: Task
> Components: api, tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Assignee: Michael Bouschen
>Priority: Major
>
> There are tons of warnungs when running the compiler in the tck with
> -Xlint:unchecked. We should fix at least some of them.
> {{}}
> {{ org.apache.maven.plugins}}
> {{ maven-compiler-plugin}}
> {{ }}
> {{ true}}
> {{ true}}
> {{ -Xlint:unchecked}}
> {{ }}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JDO-817) Check Compiler warnings
[
https://issues.apache.org/jira/browse/JDO-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-817:
-
Fix Version/s: JDO 3.2.2
> Check Compiler warnings
> ---
>
> Key: JDO-817
> URL: https://issues.apache.org/jira/browse/JDO-817
> Project: JDO
> Issue Type: Task
> Components: api, tck
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2
>
>
> There are tons of warnungs when running the compiler in the tck with
> -Xlint:unchecked. We should fix at least some of them.
> {{}}
> {{ org.apache.maven.plugins}}
> {{ maven-compiler-plugin}}
> {{ }}
> {{ true}}
> {{ true}}
> {{ -Xlint:unchecked}}
> {{ }}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JDO-817) Check Compiler warnings
Michael Bouschen created JDO-817:
Summary: Check Compiler warnings
Key: JDO-817
URL: https://issues.apache.org/jira/browse/JDO-817
Project: JDO
Issue Type: Task
Components: api, tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen
There are tons of warnungs when running the compiler in the tck with
-Xlint:unchecked. We should fix at least some of them.
{{}}
{{ org.apache.maven.plugins}}
{{ maven-compiler-plugin}}
{{ }}
{{ true}}
{{ true}}
{{ -Xlint:unchecked}}
{{ }}
{{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (JDO-814) Remove ant dependency
[ https://issues.apache.org/jira/browse/JDO-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-814. -- Resolution: Fixed > Remove ant dependency > -- > > Key: JDO-814 > URL: https://issues.apache.org/jira/browse/JDO-814 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > The api subproject has a dependency to org.apache.ant.ant and it looks like > that this is not needed anymore, so we should remove this dependency. > We shoud check whether this dependency is used in another JDO submodule. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (JDO-814) Remove ant dependency
[ https://issues.apache.org/jira/browse/JDO-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-814: Assignee: Michael Bouschen > Remove ant dependency > -- > > Key: JDO-814 > URL: https://issues.apache.org/jira/browse/JDO-814 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > The api subproject has a dependency to org.apache.ant.ant and it looks like > that this is not needed anymore, so we should remove this dependency. > We shoud check whether this dependency is used in another JDO submodule. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-812) Move to JDK 11 as the lowest supported version
[
https://issues.apache.org/jira/browse/JDO-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-812:
-
Component/s: api
site and infrastructure
tck
> Move to JDK 11 as the lowest supported version
> --
>
> Key: JDO-812
> URL: https://issues.apache.org/jira/browse/JDO-812
> Project: JDO
> Issue Type: Task
> Components: api, site and infrastructure, tck
>Affects Versions: JDO 3.2.1
>Reporter: Tobias Bouschen
>Priority: Minor
> Fix For: JDO 3.3
>
>
> I propose to move the lowest supported JDK version to JDK11 to allow us to
> move the used libraries (like Derby) to the newest version. Additionally,
> this would allow us to use some of the comfort features that were introduced
> in-between JDK 8 and 11 (like In-line Collection creation through
> {{{}List.of(...){}}}, etc.).
> From what I remember, we should already be fully compatible with JDK 11, so
> the switch itself should only require minimal effort.
> This would definitely be a breaking change, so the benefit of this change
> would have to be considered under this aspect as well (if we don't already
> have breaking changes since 3.2). A second consideration would also be when
> the next release is likely to take place (and whether JDK 8 will still be
> relevant at that point.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (JDO-812) Move to JDK 11 as the lowest supported version
[
https://issues.apache.org/jira/browse/JDO-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-812:
-
Affects Version/s: JDO 3.2.1
> Move to JDK 11 as the lowest supported version
> --
>
> Key: JDO-812
> URL: https://issues.apache.org/jira/browse/JDO-812
> Project: JDO
> Issue Type: Task
>Affects Versions: JDO 3.2.1
>Reporter: Tobias Bouschen
>Priority: Minor
> Fix For: JDO 3.3
>
>
> I propose to move the lowest supported JDK version to JDK11 to allow us to
> move the used libraries (like Derby) to the newest version. Additionally,
> this would allow us to use some of the comfort features that were introduced
> in-between JDK 8 and 11 (like In-line Collection creation through
> {{{}List.of(...){}}}, etc.).
> From what I remember, we should already be fully compatible with JDK 11, so
> the switch itself should only require minimal effort.
> This would definitely be a breaking change, so the benefit of this change
> would have to be considered under this aspect as well (if we don't already
> have breaking changes since 3.2). A second consideration would also be when
> the next release is likely to take place (and whether JDK 8 will still be
> relevant at that point.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (JDO-812) Move to JDK 11 as the lowest supported version
[
https://issues.apache.org/jira/browse/JDO-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-812:
-
Fix Version/s: JDO 3.3
> Move to JDK 11 as the lowest supported version
> --
>
> Key: JDO-812
> URL: https://issues.apache.org/jira/browse/JDO-812
> Project: JDO
> Issue Type: Task
>Reporter: Tobias Bouschen
>Priority: Minor
> Fix For: JDO 3.3
>
>
> I propose to move the lowest supported JDK version to JDK11 to allow us to
> move the used libraries (like Derby) to the newest version. Additionally,
> this would allow us to use some of the comfort features that were introduced
> in-between JDK 8 and 11 (like In-line Collection creation through
> {{{}List.of(...){}}}, etc.).
> From what I remember, we should already be fully compatible with JDK 11, so
> the switch itself should only require minimal effort.
> This would definitely be a breaking change, so the benefit of this change
> would have to be considered under this aspect as well (if we don't already
> have breaking changes since 3.2). A second consideration would also be when
> the next release is likely to take place (and whether JDK 8 will still be
> relevant at that point.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (JDO-671) Oracle spec page on JDO does not list mrel 3/JDO 3.0
[ https://issues.apache.org/jira/browse/JDO-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-671: - Fix Version/s: (was: JDO 3.3) > Oracle spec page on JDO does not list mrel 3/JDO 3.0 > > > Key: JDO-671 > URL: https://issues.apache.org/jira/browse/JDO-671 > Project: JDO > Issue Type: Improvement > Components: specification >Affects Versions: JDO 3 (3.0) >Reporter: Matthew T. Adams >Assignee: Craig L Russell >Priority: Trivial > > The page at > http://www.oracle.com/technetwork/java/index-jsp-135919.html > does not list JDO maintenance release 3 or JDO 3.0 but should. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-799) Update the jdo pom with developers
[ https://issues.apache.org/jira/browse/JDO-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-799: - Fix Version/s: JDO 3.2.2 (was: JDO 3.3) > Update the jdo pom with developers > -- > > Key: JDO-799 > URL: https://issues.apache.org/jira/browse/JDO-799 > Project: JDO > Issue Type: Improvement > Components: api, site and infrastructure, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > Update the developers list in the pom.xml in the parent-pom module. > Update the comitters list in team-list.adoc. > Both lists should in in sync. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-814) Remove ant dependency
[ https://issues.apache.org/jira/browse/JDO-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-814: - Fix Version/s: JDO 3.2.2 > Remove ant dependency > -- > > Key: JDO-814 > URL: https://issues.apache.org/jira/browse/JDO-814 > Project: JDO > Issue Type: Task > Components: api >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.2 > > > The api subproject has a dependency to org.apache.ant.ant and it looks like > that this is not needed anymore, so we should remove this dependency. > We shoud check whether this dependency is used in another JDO submodule. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (JDO-814) Remove ant dependency
Michael Bouschen created JDO-814: Summary: Remove ant dependency Key: JDO-814 URL: https://issues.apache.org/jira/browse/JDO-814 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3.2.1 Reporter: Michael Bouschen The api subproject has a dependency to org.apache.ant.ant and it looks like that this is not needed anymore, so we should remove this dependency. We shoud check whether this dependency is used in another JDO submodule. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (JDO-813) Avoid duplicated license and notice files in distribution artifact
[ https://issues.apache.org/jira/browse/JDO-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-813. -- Resolution: Fixed Renamed NOTICE.txt to NOTICE and renamed LICENSE.txt to LICENSE. > Avoid duplicated license and notice files in distribution artifact > -- > > Key: JDO-813 > URL: https://issues.apache.org/jira/browse/JDO-813 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > When building the distribution (see step 10 in HowToReleaseJDO.md) the > distribution artifact includes the license and notice files twice: > * NOTICE and NOTICE.txt > * LICENSE and LICENSE.txt > We only need one version of it. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (JDO-813) Avoid duplicated license and notice files in distribution artifact
[ https://issues.apache.org/jira/browse/JDO-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-813: Assignee: Michael Bouschen > Avoid duplicated license and notice files in distribution artifact > -- > > Key: JDO-813 > URL: https://issues.apache.org/jira/browse/JDO-813 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > When building the distribution (see step 10 in HowToReleaseJDO.md) the > distribution artifact includes the license and notice files twice: > * NOTICE and NOTICE.txt > * LICENSE and LICENSE.txt > We only need one version of it. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-813) Avoid duplicated license and notice files in distribution artifact
[ https://issues.apache.org/jira/browse/JDO-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-813: - Fix Version/s: JDO 3.2.1 > Avoid duplicated license and notice files in distribution artifact > -- > > Key: JDO-813 > URL: https://issues.apache.org/jira/browse/JDO-813 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > When building the distribution (see step 10 in HowToReleaseJDO.md) the > distribution artifact includes the license and notice files twice: > * NOTICE and NOTICE.txt > * LICENSE and LICENSE.txt > We only need one version of it. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (JDO-813) Avoid duplicated license and notice files in distribution artifact
Michael Bouschen created JDO-813: Summary: Avoid duplicated license and notice files in distribution artifact Key: JDO-813 URL: https://issues.apache.org/jira/browse/JDO-813 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3.2 Reporter: Michael Bouschen When building the distribution (see step 10 in HowToReleaseJDO.md) the distribution artifact includes the license and notice files twice: * NOTICE and NOTICE.txt * LICENSE and LICENSE.txt We only need one version of it. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-808) Java 18
[ https://issues.apache.org/jira/browse/JDO-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-808: - Fix Version/s: JDO 3.2.1 (was: JDO 3.3) > 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 > Fix For: JDO 3.2.1 > > > 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.7#820007)
[jira] [Resolved] (JDO-808) Java 18
[ https://issues.apache.org/jira/browse/JDO-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-808. -- Resolution: Fixed > 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 > Fix For: JDO 3.2.1 > > > 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.7#820007)
[jira] [Reopened] (JDO-808) Java 18
[ https://issues.apache.org/jira/browse/JDO-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reopened JDO-808: -- > 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 > Fix For: JDO 3.3 > > > 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.7#820007)
[jira] [Resolved] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-806. -- Resolution: Fixed Merge PR #1 into the spec repository > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api, specification >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (JDO-811) Update JDO dependencies
[ https://issues.apache.org/jira/browse/JDO-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-811. -- Resolution: Fixed Merge PR #46 into main > Update JDO dependencies > --- > > Key: JDO-811 > URL: https://issues.apache.org/jira/browse/JDO-811 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > There is a new version of the Apache Parent POM: 26 > We shoudl check the dependencies and plugin dependencies in the JDO parent > pom whether there are updates available. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-805) Consolidate download pages
[ https://issues.apache.org/jira/browse/JDO-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-805: - Fix Version/s: JDO 3.2.1 (was: JDO 3.3) > Consolidate download pages > -- > > Key: JDO-805 > URL: https://issues.apache.org/jira/browse/JDO-805 > Project: JDO > Issue Type: Task > Components: site and infrastructure >Reporter: Tilmann Zäschke >Assignee: Tilmann Zäschke >Priority: Major > Fix For: JDO 3.2.1 > > > From email discussion: > ??The download release pages appear to contain a lot of duplicated > information. Maybe we can consolidate them to a single download page > instead??? > ??E.g. with:?? > ??- Introduction with repo-link?? > ??- a single Maven example for the latest version?? > ??- a table with one row per version with release notes|API link|signatures; > maybe a separate table for TCK downloads?? > ??- instructions for verification?? > ??- About JDO Releases?? > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-806: - Component/s: specification > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api, specification >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (JDO-811) Update JDO dependencies
Michael Bouschen created JDO-811: Summary: Update JDO dependencies Key: JDO-811 URL: https://issues.apache.org/jira/browse/JDO-811 Project: JDO Issue Type: Task Components: api, tck Affects Versions: JDO 3.2 Reporter: Michael Bouschen There is a new version of the Apache Parent POM: 26 We shoudl check the dependencies and plugin dependencies in the JDO parent pom whether there are updates available. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (JDO-811) Update JDO dependencies
[ https://issues.apache.org/jira/browse/JDO-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-811: Fix Version/s: JDO 3.2.1 Assignee: Michael Bouschen > Update JDO dependencies > --- > > Key: JDO-811 > URL: https://issues.apache.org/jira/browse/JDO-811 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > There is a new version of the Apache Parent POM: 26 > We shoudl check the dependencies and plugin dependencies in the JDO parent > pom whether there are updates available. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Reopened] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reopened JDO-806: -- Repoen, because the spec update still needs to be done. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-806. -- Resolution: Fixed Merged PR #40 into the main branch. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-806: Assignee: Michael Bouschen > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JDO-808) Java 18
[ https://issues.apache.org/jira/browse/JDO-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-808: - Fix Version/s: JDO 3.3 > 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 > Fix For: JDO 3.3 > > > 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)
[jira] [Updated] (JDO-809) Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly map embedded element fields
[ https://issues.apache.org/jira/browse/JDO-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-809: - Fix Version/s: JDO 3.2.1 (was: JDO 3.3) > Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly > map embedded element fields > -- > > Key: JDO-809 > URL: https://issues.apache.org/jira/browse/JDO-809 > Project: JDO > Issue Type: Bug > Components: tck >Affects Versions: JDO 2 final (2.0), JDO 3 (3.0), JDO 3.1, JDO 3.2 >Reporter: Andy Jefferson >Priority: Major > Fix For: JDO 3.2.1 > > > The tests for the different java.util.Collection types all should follow the > same pattern, with the samples having a range of fields that cover the > primary field usages. > Field XXXOfObject1 should represent a Collection of Object, where the Object > is a PersistenceCapable type, persisting embedded into a join table. > Field XXXOfSimpleClass should represent a Collection of PersistenceCapable > type, persisting embedded into a join table. > Field XXXOfSimpleInterface should represent a Collection of interface, where > the interface is a PersistenceCapable type, persisting embedded into a join > table. > > In the case of the ArrayList and TreeSet cases the ORM files do not define > the block for how the fields of the PersistenceCapable element > will map into the join table. The schema for those cases also do not map the > fields of the PersistenceCapable element, instead just having a FK to the > table of the element (so not embedded at all). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JDO-809) Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly map embedded element fields
[ https://issues.apache.org/jira/browse/JDO-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-809: - Fix Version/s: JDO 3.3 > Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly > map embedded element fields > -- > > Key: JDO-809 > URL: https://issues.apache.org/jira/browse/JDO-809 > Project: JDO > Issue Type: Bug > Components: tck >Affects Versions: JDO 2 final (2.0), JDO 3 (3.0), JDO 3.1, JDO 3.2 >Reporter: Andy Jefferson >Priority: Major > Fix For: JDO 3.3 > > > The tests for the different java.util.Collection types all should follow the > same pattern, with the samples having a range of fields that cover the > primary field usages. > Field XXXOfObject1 should represent a Collection of Object, where the Object > is a PersistenceCapable type, persisting embedded into a join table. > Field XXXOfSimpleClass should represent a Collection of PersistenceCapable > type, persisting embedded into a join table. > Field XXXOfSimpleInterface should represent a Collection of interface, where > the interface is a PersistenceCapable type, persisting embedded into a join > table. > > In the case of the ArrayList and TreeSet cases the ORM files do not define > the block for how the fields of the PersistenceCapable element > will map into the join table. The schema for those cases also do not map the > fields of the PersistenceCapable element, instead just having a FK to the > table of the element (so not embedded at all). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JDO-807) Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition
[ https://issues.apache.org/jira/browse/JDO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-807: - Fix Version/s: (was: JDO 3.3) > Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition > -- > > Key: JDO-807 > URL: https://issues.apache.org/jira/browse/JDO-807 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0 schema > descrpitor: > http://java.sun.com/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo > [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> > This should be updated to use the 3.2 version: > .jdo-files: > http://xmlns.jcp.org/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo > [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> > .orm-files: > http://xmlns.jcp.org/xml/ns/jdo/orm; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm > [http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd];> > .jdoquery-files > http://xmlns.jcp.org/xml/ns/jdo/jdoquery; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery > [http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd];> -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-806: - Fix Version/s: JDO 3.2.1 (was: JDO 3.3) > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (JDO-807) Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition
[ https://issues.apache.org/jira/browse/JDO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-807. -- Fix Version/s: JDO 3.2.1 Resolution: Fixed Merged PR # 39 into main. > Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition > -- > > Key: JDO-807 > URL: https://issues.apache.org/jira/browse/JDO-807 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.2.1, JDO 3.3 > > > Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0 schema > descrpitor: > http://java.sun.com/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo > [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> > This should be updated to use the 3.2 version: > .jdo-files: > http://xmlns.jcp.org/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo > [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> > .orm-files: > http://xmlns.jcp.org/xml/ns/jdo/orm; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm > [http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd];> > .jdoquery-files > http://xmlns.jcp.org/xml/ns/jdo/jdoquery; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery > [http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd];> -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-807) Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition
[ https://issues.apache.org/jira/browse/JDO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510092#comment-17510092 ] Michael Bouschen commented on JDO-807: -- You are right, Andy. But I have this change in my workspace already. So I plan to do this in two steps. BTW, is DataNuclues always using a local copy of the schema descriptors (xsd or dtd) and then always uses the latest version? We were wondering why the converter examples work w/o any issue, altough I used the 3.0 version of the xsd schema descriptor, but converters were added in 3.2. > Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition > -- > > Key: JDO-807 > URL: https://issues.apache.org/jira/browse/JDO-807 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0 schema > descrpitor: > http://java.sun.com/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo > [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> > This should be updated to use the 3.2 version: > .jdo-files: > http://xmlns.jcp.org/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo > [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> > .orm-files: > http://xmlns.jcp.org/xml/ns/jdo/orm; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm > [http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd];> > .jdoquery-files > http://xmlns.jcp.org/xml/ns/jdo/jdoquery; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery > [http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd];> -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JDO-807) Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition
[ https://issues.apache.org/jira/browse/JDO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-807: - Description: Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0 schema descrpitor: http://java.sun.com/xml/ns/jdo/jdo; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> This should be updated to use the 3.2 version: .jdo-files: http://xmlns.jcp.org/xml/ns/jdo/jdo; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> .orm-files: http://xmlns.jcp.org/xml/ns/jdo/orm; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm [http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd];> .jdoquery-files http://xmlns.jcp.org/xml/ns/jdo/jdoquery; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery [http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd];> was: Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0scheema descrpitor: http://java.sun.com/xml/ns/jdo/jdo; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> This should be updated to use the 3.2 version: .jdo-files: http://xmlns.jcp.org/xml/ns/jdo/jdo; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> .orm-files: http://xmlns.jcp.org/xml/ns/jdo/orm; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd;> .jdoquery-files http://xmlns.jcp.org/xml/ns/jdo/jdoquery; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd;> > Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition > -- > > Key: JDO-807 > URL: https://issues.apache.org/jira/browse/JDO-807 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > Most of the JDO metadata files (.jdo, .jdoquery, .orm) use the 3.0 schema > descrpitor: > http://java.sun.com/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://java.sun.com/xml/ns/jdo/jdo > [http://java.sun.com/xml/ns/jdo/jdo_3_0.xsd];> > This should be updated to use the 3.2 version: > .jdo-files: > http://xmlns.jcp.org/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo > [http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd];> > .orm-files: > http://xmlns.jcp.org/xml/ns/jdo/orm; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/orm > [http://xmlns.jcp.org/xml/ns/jdo/orm_3_2.xsd];> > .jdoquery-files > http://xmlns.jcp.org/xml/ns/jdo/jdoquery; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoquery > [http://xmlns.jcp.org/xml/ns/jdo/jdoquery_3_2.xsd];> -- This message was sent by Atlassian Jira (v8.20.1#820001)
