Thank you Thomas! The parallel solution worked or me. And thanks for the other
replies too.
For the record, the second jetty instance must use the run-forked goal, because
the ShutdownMonitor thread in jetty is declared static. A design flaw in my
opinion. Trying to run a second jetty
There's Cuppa which is super cool and allows to control such things to a
very fine level.
https://github.com/cuppa-framework/cuppa/
It is not clear that Cuppa has multi-year life though. I wish it did.
On Thu, Oct 11, 2018 at 10:21 PM Ellis, Scott
wrote:
> Hi,
>
> I have a project that builds
Alternatively, if possible, you could possibly run the app with both
configurations in parallel (two executions of jetty-maven-plugin in
pre-integration-test and post-integration-test phase, using different
ports), and run you tests twice, for each app / port (two executions of
failsafe at
I'd say you need two modules; one for each IT setup. Each module is a Maven
project and will then run the integration tests. The actual integration
test code could then be in a third module and you declare a dependency on
that artifact.
/Anders
On Thu, Oct 11, 2018 at 11:21 PM Ellis, Scott
