[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218722#comment-15218722 ]
Quinn Stevenson commented on CAMEL-6132: ---------------------------------------- The first iteration on this will create the camel-test-karaf module, and move the AbstractFeatureTest class from the camel-itest-karaf module to the new camel-test-karaf module. I'm also going to include some of the configuration to help keep the Karaf instances from hanging around after the tests. I should have the PR ready tomorrow > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > ------------------------------------------------------------------------------------- > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf > Reporter: Claus Ibsen > Assignee: Quinn Stevenson > Fix For: Future > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.4#6332)