Hello ! Well, I understand from your answer that another module exists for junit5 with classes that are not deprecated. I've just changed my dependency to "camel-test-blueprint-junit5" and indeed warnings disappeared.
I also had to make some changes for mockito, runner, etc., but now my tests fail with exceptions that I had not before, as if the blueprint test lifecycle had changed... I'm going to check that on my side... I didn't guess that I had to search for renamed artifacts :(... Thanks for your help. Regards. Le lun. 2 janv. 2023 à 14:10, Santiago Acosta <santiago.aco...@intermodaltelematics.com> a écrit : > > You made me worry so I went looking for > https://github.com/apache/camel/blob/main/components/camel-test/camel-test-junit5/src/main/java/org/apache/camel/test/junit5/CamelTestSupport.java > - on Branch main > - for Framework Junit5 > and it does not have a deprecation notice. > What CamelTestSupport are you currently using? > > On Thu, Dec 29, 2022 at 11:52 AM Ephemeris Lappis < > ephemeris.lap...@gmail.com> wrote: > > > Hello. > > > > One more surprise with Camel 3.x. The class CamelTestSupport has been > > deprecated, while CamelBlueprintTestSupport seems to use it with no > > depreciation. > > > > I can't find any valid replacement to test blueprint contexts. Did I > > miss something ? Should we use deprecated code for tests ? > > > > Thanks again ! > > > > Regards. > > > > > -- > Best regards, > *Santiago Acosta Arreaza* > > Intermodal Telematics S.L. > Prisma building, 1st floor, Office 1.5 > Fotógrafo José Norberto Rguez. Díaz st., 2 > San Cristobal de La Laguna, SC de Tenerife > 38204, Spain > > > +34 922 31 56 05 > www.intermodaltelematics.com
