Hi all, After some consideration, I have decided to halt this change. What we have now is enough of a cleanup and, IMHO, removing the deprecated methods would unnecessarily violate one of the goals we had for Camel 4 (to be as close as possible a drop-in replacement for 3.x). Additionally, I think there are other areas in and around Camel that need more focus right now. I might revive this some point in the future when/if it becomes safe to remove these methods.
Kind regards On Thu, Oct 3, 2024 at 2:40 PM Otavio Rodolfo Piske <angusyo...@gmail.com> wrote: > Some weeks ago I wrote a blog post about upcoming changes to base test > classes used by Camel [1]. > > Hi, > > Now that Camel 4.8 is out, I would like to start cleaning those deprecated > interfaces and finishing the task. However, it's critical to do so in a way > that is the least disruptive as possible. We want to make our life easier, > not yours harder! > > Here I need a bit of help from the community. Today I submitted a draft PR > [2] with the proposal to remove the deprecated interfaces and introduce > some utilities to simplify the migration. The idea is to show the set of > proposed changes and collect feedback. I am initially aiming for 4.10, but > ultimately it will depend on what I hear from the community. > > So, if you have extensive test code relying on CamelTestSupport or > CamelSpringTestSupport ... do take a look at that, comment on the PR and > let me know what you think. > > 1. https://camel.apache.org/blog/2024/09/modernizing-test-support/ > 2. https://github.com/apache/camel/pull/15830 > > Kind regards > -- > Otavio R. Piske > http://orpiske.net > -- Otavio R. Piske http://orpiske.net
