| Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central |
JAX-RS 2.1.1 _did not_ add any features due to EF's target to simply repeat the feature set of Java EE 8. In JAX-RS 2.2 (planned for later this year) I have added a complete new API which covers a feature which had been there already existing in Jersey, but was hidden behind a native API. If a package name change is needed, the EMO ("Eclipse Legal") will tell us. Until then, we just keep the package names as-is. -Markus From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil Did you add an entirely new element (interface or other) to the JAX-RS API that wasn’t there before? The discussion still does not seem complete, but from what I heard so far also in the Spec Committee, if JAX-RS 2.1.1 added an entirely new element under javax.ws.rs, basically anything that would go beyond a simple Maintenance Release (MR) in the JCP, then this new element must be introduced under the new namespace (presumably “jakarta.rs” or “jakarta.ws.rs” for consistency) Werner Sent from Mail for Windows 10 From: Markus KARG Unfortunately this is not the EFs official policy. According to EF president Mike Milinkovic, all EE4J API projects shall NOT force features from vendors, but instead shall only wrap existing features under a common hood. What I did is adding feature to API AND to Jersey parallel, and encouraged other vendors to follow. -Markus From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Mihai A. Well, from my point of view, the API should add features and force implementors to keep up. If we only ask for a feature from RestEasy, then the whole point of JAX-RS is gone... but I guess that's a neverending discussion. Thanks, Mihai On Sun, Sep 9, 2018, 09:31 Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
_______________________________________________ |