Hi Olivier,
OK I will take a look and thanks for the pointer.
Cheers,
Chris
On Oct 1, 2012, at 8:27 AM, Olivier Lamy wrote:
> Chris,
> If you can use tomcat maven plugin rather than jetty.
> It's possible to use port 0 (which means jvm will use the first available
> port).
> I don't know exact
Chris,
If you can use tomcat maven plugin rather than jetty.
It's possible to use port 0 (which means jvm will use the first available port).
I don't know exactly what your build do so I cannot tell you if that's
possible or not for your use case.
But in Archiva project, we start an embeded tomcat
Hey Brett,
Thanks! I was able to resolve this by finding the same helper plugin
independently via
a few Google searches. That fixed it!
Thanks man!
Cheers,
Chris
On Oct 1, 2012, at 6:38 AM, Brett Porter wrote:
> Chris,
>
> This sounds like you've had some jobs hang that held on to the port,
Chris,
This sounds like you've had some jobs hang that held on to the port, as it'd be
unlikely another project is using the same port.
If you need to make sure you get distinct ports, try:
http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
Either way, if the buil
Hey Martin,
I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
in Apache SIS to do automatic Jetty testing. I found this code snippet:
{code}
start-jetty
pre-integration-test
run
