On Mar 22, 2010, at 4:57 PM, Pierce T. Wetter III wrote: > > On Mar 22, 2010, at 3:22 PM, Michael Gentry wrote: > >> I don't know what container you are using, but with Jetty, I do something >> like: >> >> mvn -Djetty.port=5555 jetty:run > > It's the self tests in the tapestry T5.2 build, but I'll try that... Cool. > my hudson build now builds and deploys into nexus again.
Doh! Spoke too soon. Mostly, jetty seems to run on port 9999, ignoring the above setting. But turns out I'm getting a conflict with selenium on port 4444 anyways. Pierce --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
