Why don't you just write a unit test base class that runs Jetty embedded? If you store the server in a static attribute and start it in @BeforeClass (or similar) conditionally if hasn't been started before, you'll save the restart costs between each test. As a bonus, these integration tests are easily runnable from your IDE. This is exactly what I do.
Kalle On Mon, May 18, 2009 at 9:16 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hey, before you think this guy is crazy, surefire will do that for you... > > pre-integration-test: jetty:run daemon=true > integration-test: surefire:test testFailureIgnore=true > post-integration-test: jetty:stop > verify: ______:______ > > so that I can run my integration tests and tidy-up afterwards and then fail > the build after the tidy-up... > > yes, yes, yes I know about putting the tests in a separate module and all > that jazz... but this is in some ways a bit cleaner > > -Stephen >
