You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Mark Struberg (Jira)" <ji...@apache.org> on 2020/02/29 15:06:00 UTC
[jira] [Reopened] (OPENJPA-2798) OpenJPA need to be more Java11
friendly
[ https://issues.apache.org/jira/browse/OPENJPA-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg reopened OPENJPA-2798:
------------------------------------
sorry this is a no-go. We have our own impl which is also fine from a license perspective. EPL is cat-b and requires attribution. basically weak-copyleft. I see no reason to add this when we have our own impl.
> OpenJPA need to be more Java11 friendly
> ---------------------------------------
>
> Key: OPENJPA-2798
> URL: https://issues.apache.org/jira/browse/OPENJPA-2798
> Project: OpenJPA
> Issue Type: Improvement
> Components: third-party
> Affects Versions: 3.1.0
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In case one will add OpenJPA as a dependency to Java11 modularized project the following issue will arise:
> openjpa depends on "Apache Geronimo JPA Spec 2.2"
> geronimo jpa doesn't have automatic module name and automatically being resolved as
> geronimo.jpa.2.2.spec
> Which is invalid java identifier :(((
> I believe OpenJPA should be more Java11 friendly
--
This message was sent by Atlassian Jira
(v8.3.4#803005)