You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2020/02/29 15:14:00 UTC

[jira] [Commented] (OPENJPA-2798) OpenJPA need to be more Java11 friendly

    [ https://issues.apache.org/jira/browse/OPENJPA-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048327#comment-17048327 ] 

Romain Manni-Bucau commented on OPENJPA-2798:
---------------------------------------------

Well, we dont deliver it so not that critical both ways (whatever api we depend on, it is likely not the one apps will run with), however this issue is about ensuring we have automatic module *for openjpa* and a standard module name for geronimo (as another issue likely).

That said it is low priority since nobody uses jpms for real world projects, osgi metadata stays way more important than jpms from what I can see.

 

That said i join Mark for our assembly, the legal work hasnt been done so we should keep geronimo jar there at minimum - being said having the same everywhere is indeed better but no fight here for me since it does not affect consumers.

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