By default the pax:run mojo starts the container and waits for the user to manually stop it. That works great for manually testing things, but to develop webapps or other apps based on OSGi it would be nice to be able to run pax runner in a separate thread or process. Then you could start up the container during pre-integration-tests, do you're integration testing using HTMLUnit or something else in the integration-test phase, and run a pax:stop goal in the post-integration-tests phase that would stop the container. This is similar in principle to how the maven-cargo-plugin works.
Richard Wallace created PAXCONSTRUCT-113
By default the pax:run mojo starts the container and waits for the user to manually stop it. That works great for manually testing things, but to develop webapps or other apps based on OSGi it would be nice to be able to run pax runner in a separate thread or process. Then you could start up the container during pre-integration-tests, do you're integration testing using HTMLUnit or something else in the integration-test phase, and run a pax:stop goal in the post-integration-tests phase that would stop the container. This is similar in principle to how the maven-cargo-plugin works.
Fixed in: 1.7.0 Votes: 1, Watches: 1