I am not quite convinced that it is a backwards compatible change (but I may be wrong). If you deprecate @Context in JAX-RS 2.2, but do not mandate CDI at the same time, what does the Javadocs actually tell people to use instead…? From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of arjan tijms
Sent: Montag, 23. Juli 2018 20:45
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] [Discuss] Initial Roadmap / Preliminary Release Schedule Hi, Thanks for clarifying. I've created an issue to discuss deprecation [1]. Could you please set the milestone to 3.0?
I'd actually like to suggest doing this for 2.2, as it's a backwards compatible change. Then in 3.0 we can actually remove @Context, which would be a non-backwards compatible change which would be allowed in a major release. Guillermo González de agüero Guillermo, yes, if we remove something in 3.0 then we MUST deprecate it in 2.2 or 2.1.1. But this has to be voted. IIRC we have not yet voted about any particular content of neither 3.0 nor 2.2 nor 2.1.1, so I just picked what I understood to be common sense of the various discussions so far. Feel free to open an issue wrt deprecating @Context and set the linked milestone to 3, which effectively opens the possibility for reviewing and voting. -Markus Hi Markus, Thanks for getting it written. Does 3.0 imply *removing* @Context and other related stuff. If so, those features should be deprecated in a previous version to give users a chance to migrate. _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
|
