[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rest-dev] [External] : @Context removal vs. deprecation
|
FWIW I'm okay with either the deprecation happening in 4.1 or a 5.0. That said, I do understand the desire to deprecate in 5.0 and remove in 6.0. It could help implementations handle the breaking changes a bit better so they themselves could break some compatibility.
Personally
I prefer deprecation in a 5.0 (EE12) release prior to removal in a 6.0 release. That would help us with the possible compatibility issues related to the discussed CDI beans and Application methods.
--Jan
Hi,
Assuming there are no problems, we can consider the 4.0 content to be set. And, at least for now, that work will continue in the “main” branch.
That brings us to the discussion of what will be next. Do we push for a version 5.0 that removes @Context injection entirely or a 4.1 version that deprecates @Context injection and provides an alternative implementation? Both of these options carry
many/most of the same concerns and some good progress has been made in the “release-3.2” branch toward deprecation..
So the question is, should this deprecation work continue in a “release-4.1” working branch or be abandon in favor of a “release-5.0” that removes @Context injection.
Personally I prefer deprecation in a 4.1 release prior to removal in a 5.0 release, unless a blocking issue is discovered. What is your opinion?
Thanks
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
-- James R. Perkins
JBoss by Red Hat
