You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andy McCright (Jira)" <ji...@apache.org> on 2020/06/11 02:54:00 UTC

[jira] [Comment Edited] (CXF-8075) Plan for CXF 3.4.0 release

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

Andy McCright edited comment on CXF-8075 at 6/11/20, 2:53 AM:
--------------------------------------------------------------

Just FYI - The plans for JAX-RS 2.2 have changed.  The agreement with Oracle won't allow new APIs under the `javax.*`* package space, so the Jakarta community decided that all projects must release a new major release (under Jakarta EE 9) that uses the `jakarta.` package space.  The Jakarta community also decided that the package rename should be the only functional change to go in to the next release.  

The JAX-RS (now called Jakarta RESTful Web Services) community decided that it will release JAX-RS 3.0 (a milestone build is available in Maven Central) that only includes the package rename (it also includes clarifications in the spec and javadoc, but no changes to the API other than the package).  Soon after 3.0 is released, the community will release 3.1 which will include the features previously targeted for 2.2 and possibly more.  

I mention this for two reasons: (1) without any new 2.2 release, there may not be much reason to wait on the 3.4.0 release, and (2) we had previously discussed that CXF 4.0 might implement the latest Jakarta EE 9 specs (with the package rename) since it is a breaking change.  I'm fine with whatever is decided (3.5.0 or 4.0), but just wanted to make sure we all had the same info.

 

One other thing going into 3.4.0 is MicroProfile Rest Client 2.0.  That's another tricky thing... the MP community is halting GA releases until they can setup the Working Group within the Eclipse community.  They are looking for other vendors to join, so if your company's are interested, let me know - I don't have a lot of details, but I can connect you with people who do.  But what that means at this moment is that the MP Rest Client 2.0 work (most of which is integrated into master) is all based on release candidate builds, not GA builds.  I've heard predictions that we should be able to GA in August, but that is not a concrete date...   

 

Sorry to be the bearer of (mostly) bad news... If there's anything I can help with on these issues, please let me know.  Thanks!


was (Author: amccright):
Just FYI - The plans for JAX-RS 2.2 have changed.  The agreement with Oracle won't allow new APIs under the `javax.*` package space, so the Jakarta community decided that all projects must release a new major release (under Jakarta EE 9) that uses the `jakarta.*` package space.  The Jakarta community also decided that the package rename should be the only functional change to go in to the next release.  

The JAX-RS (now called Jakarta RESTful Web Services) community decided that it will release JAX-RS 3.0 (a milestone build is available in Maven Central) that only includes the package rename (it also includes clarifications in the spec and javadoc, but no changes to the API other than the package).  Soon after 3.0 is released, the community will release 3.1 which will include the features previously targeted for 2.2 and possibly more.  

I mention this for two reasons: (1) without any new 2.2 release, there may not be much reason to wait on the 3.4.0 release, and (2) we had previously discussed that CXF 4.0 might implement the latest Jakarta EE 9 specs (with the package rename) since it is a breaking change.  I'm fine with whatever is decided (3.5.0 or 4.0), but just wanted to make sure we all had the same info.

 

One other thing going into 3.4.0 is MicroProfile Rest Client 2.0.  That's another tricky thing... the MP community is halting GA releases until they can setup the Working Group within the Eclipse community.  They are looking for other vendors to join, so if your company's are interested, let me know - I don't have a lot of details, but I can connect you with people who do.  But what that means at this moment is that the MP Rest Client 2.0 work (most of which is integrated into master) is all based on release candidate builds, not GA builds.  I've heard predictions that we should be able to GA in August, but that is not a concrete date...   

 

Sorry to be the bearer of (mostly) bad news... If there's anything I can help with on these issues, please let me know.  Thanks!

> Plan for CXF 3.4.0 release
> --------------------------
>
>                 Key: CXF-8075
>                 URL: https://issues.apache.org/jira/browse/CXF-8075
>             Project: CXF
>          Issue Type: Task
>            Reporter: Andriy Redko
>            Assignee: Andriy Redko
>            Priority: Major
>             Fix For: 3.4.0
>
>
> There are multiple goals targeted for 3.4.0:
>  - align with Jakarta EE (switch to new artifacts / packages)
>  - JAX-RS 2.2, snapshots already available (https://headcrashing.wordpress.com/2019/06/25/jax-rs-2-2-nightly-builds-available/)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)