sorry, should have read your question better. So you got
multiple webapps running now with mvn jetty:run and the
remaining use case is to have different webapps listening on
different ports? I've never tried that with mvn jetty:run. I
think it should be possible. Have a look at the Configuring
Containers section on the link I've pasted below. You can
set multiple connectors. I guess all contextPaths will be
available on all connectors then.
However, if you get stuck with maven-jetty-plugin it might
be an alternative to embed jetty for your integration tests:
Hey Thomas,
I've found this docu, but there is now
documentation on how to run multiple webapps.
And the simple cases don't work for me ;-(
For the example "Running a
Pre-assembled WAR with mvn jetty:deploy-war" I
get the following error:
2011-03-02 10:42:14.118:WARN::FAILED
org.eclipse.jetty.security.ConstraintSecurityHandler@1092447:
java.lang.IllegalStateException: No LoginService
for
org.eclipse.jetty.security.authentication.BasicAuthenticator@4a0ac5
in
org.eclipse.jetty.security.ConstraintSecurityHandler@1092447
I've a Integartiontest project with some
integrationtests which need one webApp to run on
port 8080.
Another one witch need >1 webApps to run on
port 8080. And one more, that should have webapps
on port 8080 and some other webApps on port 8090.
With the "old" maven-jetty-plugin the firts two
useCases are no problem. with
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>7.3.0.v20110203</version>
it seems to be not so easy anymore ,-(