Hi Cameleers, I brought up the issue of naming the JUnit 5 component without the version and with 'jupiter' instead. The reason I brought this up is because I think that we should shield the users from version changes as much as possible. A version neutral name would allow us to move to a future JUnit version without any migration step required for the user, well, depending on the amount of backward breaking changes in the future version. I'm afraid that we'll then create -junit6 component when that version is released.
I don't mind if it's called -junit5, I would prefer if it didn't include any version information for the reason stated above. zoran On Tue, Aug 6, 2019 at 5:08 PM Alex Dettinger <aldettin...@gmail.com> wrote: > > Hi guys, > > I've started the development of a new module adding the possibility to > write base camel-test with JUnit5. So far, I've named the module > camel-test-junit5, which would lead to a family of name like > camel-test-junit5-spring, camel-test-junit5-spring-boot... > > I would like to trigger a discussion around the naming of this module as > other candidate are also valid. For instance: > camel-test-jupiter > camel-test-junit-jupiter > > > https://github.com/apache/camel/pull/3084 > https://issues.apache.org/jira/browse/CAMEL-13826 -- Zoran Regvart
