You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Bram (Jira)" <ji...@apache.org> on 2022/06/24 20:14:00 UTC

[jira] [Commented] (MRM-2031) Switch to JDK 11

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

Bram commented on MRM-2031:
---------------------------

[~martin_s] Is there any particular reason for a switch to Jakarta EE before switching to JDK 11 (or maybe 17, now)? 

Migrating from JDK8->11 is pretty straightforward. Jakarta EE on the other hand is a pretty significant switch.

Things like javax.xml, javax.ws etc are still available on JDK 11, they just require a couple of extra dependencies.

> Switch to JDK 11
> ----------------
>
>                 Key: MRM-2031
>                 URL: https://issues.apache.org/jira/browse/MRM-2031
>             Project: Archiva
>          Issue Type: Improvement
>            Reporter: Martin Schreier
>            Assignee: Martin Schreier
>            Priority: Major
>             Fix For: 3.0.0
>
>
> We should use JDK 11 as baseline, if the libraries and build process work.
> This is possible only after switching to Jakarta EE 9.x



--
This message was sent by Atlassian Jira
(v8.20.7#820007)