aldettinger commented on pull request #2739: URL: https://github.com/apache/camel-quarkus/pull/2739#issuecomment-856923967
Ok, great to know that the test is needed and that we caught up another native issue :+1: Related to point 3, I agree that having tests with a new context could help in such a situation. To my knowledge, there is no example for that in camel-quarkus. The only ideas I would have would be to create a new itest project or maybe investigate if something could be done with [quarkus test profile](https://quarkus.io/guides/getting-started-testing#testing_different_profiles). I'm not sure about point 2, could you please confirm my understanding ? My understanding would be that we override the fallback converter, then we set the global options, then the converter is initialized on next call to `convertTo()` and from there will not change afterward. So, the overridden fallback converter is sometimes present when other tests are executed. But I guess that's no big deal because other tests are assumed not to use the fallback converter ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
