You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@johnzon.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2022/11/04 08:05:00 UTC

[jira] [Closed] (JOHNZON-385) Johnzon and the javax -> jakarta namespace Migration

     [ https://issues.apache.org/jira/browse/JOHNZON-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau closed JOHNZON-385.
--------------------------------------
    Resolution: Duplicate

> Johnzon and the javax -> jakarta namespace Migration
> ----------------------------------------------------
>
>                 Key: JOHNZON-385
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-385
>             Project: Johnzon
>          Issue Type: Improvement
>            Reporter: Johan Steenkamp
>            Priority: Critical
>
> Good day.
> As you might be well aware, the Eclipse foundation took over JavaEE, which meant that all imports where you use javax.* need to change to jakarta.*.
> I have seen that many of the projects under the Apache have already provided new versions of their libraries where they have pulled dependencies from JavaEE and moved to JakartaEE instead.
> I would like to know if the Johnzon project also has plans to move all their dependencies from javax.* to jakarta.*?
> Our company is current checking if our software is compatible with Wildlfy 27 Alpha, where of the fundamental changes is also the javax.* to jakarta.* namespace change.
> We have been using the Johnzon library for quite some time now, and we are very happy with this library, but once we move over to Wildfly 27, we would not be able to use this ibrary any more because of this namespace change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)