You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Thomas Hoffmann (Jira)" <ji...@apache.org> on 2022/04/15 18:47:00 UTC

[jira] [Commented] (MRM-2030) Switch to Jakarta EE 9.x

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

Thomas Hoffmann commented on MRM-2030:
--------------------------------------

Hello Martin,

according to CXF website, it is compatible with Java 11 and Java 17:

[https://cxf.apache.org/docs/35-migration-guide.html]

[https://cxf.apache.org/docs/33-migration-guide.html]

I also migrated one project to Java17/Tomcat 10 and I had similar issues with javax and jakarta packages.

The complicated part was to find all the jars/libs which use the old javax package. After removing/updating every jar,

which used javax.... i could finally run my programm again.

Maybe you can check which jar is still using javax and try to remove/replace it.

Greetings, Thomas

> Switch to Jakarta EE 9.x
> ------------------------
>
>                 Key: MRM-2030
>                 URL: https://issues.apache.org/jira/browse/MRM-2030
>             Project: Archiva
>          Issue Type: Improvement
>            Reporter: Martin Schreier
>            Assignee: Martin Schreier
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Goal is Jakarta EE 9.1, or 9.0 if this is not feasible.
> Todo:
>  * Namespace Change
>  * Update of API Libraries
>  * Check, if OpenJPA is still compatible
>  * Use new jetty version (11)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)