No problem :-) If the server emulator is not released under one of the following licenses https://www.apache.org/legal/resolved#category-a we cannot use it in an Apache Project.
So you have to skip the integration tests for the moment (or better define a profile for integration tests) and add notes in the documentation about the way people can run integration tests and how to the setup the enviroment. Once the server emulator will be released under one of the Apache Compatible License we will add it to the component you're currently working on. Split tests between unit and integration tests is always a good practice (in this case is the only way to distinguish between server emulator based tests and not). I hope this helps. If you have questions I'm here :-) Thanks. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: [email protected] Twitter: @oscerd2 Github: oscerd On Thursday, October 27, 2016 12:19 PM, Evgeny M <[email protected]> wrote: Thank you. Will do. Would I impose too much if I also ask the following questions: • Some tests rely on the server emulator running in the background. Currently the emulator is started before the maven test phase and shut down after. Is it acceptable? Or should I exclude such integration tests into a separate profile? • The server emulator is a JAR which is not available through maven ecosystem as yet. It is proprietary. The code might be released in the future, but there is no confirmation as yet. Is it OK to include it in a projects folder - i.e. libtest? Not sure how licensing affects this. What is the alternative in terms of testing? Or should I keep the tests, but exclude them from the normal round, just provide the doco how to obtain and start emulator? • OnCompletion might raise a RuntimeException - should it be caught instead? It might result in a duplicate message as the server will resend the message that was not acknowledged. • Should I split integration (relying on the server emulator) and unit (not relying) tests? -- View this message in context: http://camel.465427.n5.nabble.com/New-component-comtribution-guidance-required-tp5789174p5789335.html Sent from the Camel Development mailing list archive at Nabble.com.
