[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Fix Version/s: 4.0.0 (was: 3.4.0) > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Epic > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Minor > Fix For: 4.0.0 > > > 3.3.0 is the last release to support JDO. > We are removing all the Causeway *-jdo artifacts. > see https://github.com/ecpnv-devops/jdo2jpa to help with migration using Open > Rewrite -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Description: 3.3.0 is the last release to support JDO. We are removing all the Causeway *-jdo artifacts. see https://github.com/ecpnv-devops/jdo2jpa to help with migration using Open Rewrite was: 3.3.0 is the last release to support JDO. We are removing all the Causeway *-jdo artifacts. > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Epic > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Minor > Fix For: 3.4.0 > > > 3.3.0 is the last release to support JDO. > We are removing all the Causeway *-jdo artifacts. > see https://github.com/ecpnv-devops/jdo2jpa to help with migration using Open > Rewrite -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Description: 3.3.0 is the last release to support JDO. We are removing all the Causeway *-jdo artifacts. was: While not yet ditching DataNucleus as supported persistence layer, we could however deprecate JDO annotations in favor of https://github.com/datanucleus/datanucleus-api-jakarta , such that users can migrate to JPA programming model perhaps more smoothly. Ideal outcome would be, that users then can chose EclipseLink, DataNucleus or Hibernate as JPA providers, while the programming model is identical. In turn we can then deprecate all Causeway *-JDO artifacts. (This Jira Question can later be turned into an Improvement.) > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Epic > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Minor > Fix For: 3.4.0 > > > 3.3.0 is the last release to support JDO. > We are removing all the Causeway *-jdo artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Issue Type: Epic (was: Question) > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Epic > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 3.4.0 > > > While not yet ditching DataNucleus as supported persistence layer, we could > however deprecate JDO annotations in favor of > https://github.com/datanucleus/datanucleus-api-jakarta > , such that users can migrate to JPA programming model perhaps more smoothly. > Ideal outcome would be, that users then can chose EclipseLink, DataNucleus or > Hibernate as JPA providers, while the programming model is identical. > In turn we can then deprecate all Causeway *-JDO artifacts. > (This Jira Question can later be turned into an Improvement.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Priority: Minor (was: Major) > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Epic > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Minor > Fix For: 3.4.0 > > > While not yet ditching DataNucleus as supported persistence layer, we could > however deprecate JDO annotations in favor of > https://github.com/datanucleus/datanucleus-api-jakarta > , such that users can migrate to JPA programming model perhaps more smoothly. > Ideal outcome would be, that users then can chose EclipseLink, DataNucleus or > Hibernate as JPA providers, while the programming model is identical. > In turn we can then deprecate all Causeway *-JDO artifacts. > (This Jira Question can later be turned into an Improvement.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAUSEWAY-3866) Removal of JDO Integration
[ https://issues.apache.org/jira/browse/CAUSEWAY-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated CAUSEWAY-3866: - Summary: Removal of JDO Integration (was: Deprecation of JDO annotations.) > Removal of JDO Integration > -- > > Key: CAUSEWAY-3866 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3866 > Project: Causeway > Issue Type: Question > Components: Persistence JDO >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 3.4.0 > > > While not yet ditching DataNucleus as supported persistence layer, we could > however deprecate JDO annotations in favor of > https://github.com/datanucleus/datanucleus-api-jakarta > , such that users can migrate to JPA programming model perhaps more smoothly. > Ideal outcome would be, that users then can chose EclipseLink, DataNucleus or > Hibernate as JPA providers, while the programming model is identical. > In turn we can then deprecate all Causeway *-JDO artifacts. > (This Jira Question can later be turned into an Improvement.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
