That's correct, but you'll then have to query the content handler object for it's currently running port.
I'm going to keep pimping out this solution I built for some clients and open sourced a while back. In one project I have an api for starting up a jetty application server either off of the eclipse compiled classpath or based on a war file found in your target directory (you can implement an interface to construct new methods of application look up). I have some fluent API code I will be pushing in to this soon. Personally I don't believe we should ever be starting jetty from maven pom files, rather that task should be done as part of test start-up, and preferable reused across all tests hitting that app. Which would allow tests to be easily run from with in eclipse (starting the webapp when needed, and allowing hot code replacement when debugging). This just ends up making devs more productive. I've got that capability, as well as retaining complex, reusable testing components through the full test execution here: https://github.com/rexhoffman/test-extensions For the eclipse based mechanism to work, simply add a webapps.properties file to your src/main/resource dir, and the util will pull web-content from src/main/webapp/ or WebContent/ I'll be adding more doc to these in the next couple weeks, but the tests should be good enough examples to get this going if anyone is interested. I will also answer questions. I really, really want to see maven plugins like jetty/tomcat/cassandra/etc die off. A good util package added in to tests to start applications locally prior to testing is more usable, more easily debuggable, and just plain cleaner. A good api on them wouldn't let the developer set a port, but instead only query the randomly selected port. Preventing threading issues like this. File system access should also be carefully managed by a java api used by developers, that prevents garbage being left in target dir or some other resource path that might interfere with other tests. My long winded 2 cents. Oh and I do have a ticket open to push this to central, and these are apache licensed. Feel free to copy. Rex On Sun, Jul 31, 2011 at 1:08 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > afaik since always. standard socket.open(port) behaviour when port is 0. > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 31 Jul 2011 20:00, "Mark Struberg" <strub...@yahoo.de> wrote: > > yea, that is good news. Will try to tweak this for all wagon tests too. > > Do you know since when this works? Is this available in jetty-6.1.26? > > > > Btw, when going through our Tests I found lots of tests which do not > cleanup the target/local-repo (or similar) before they run. Some of them > only work because they work on left-overs from previous tests. This is > pretty dangerous and should get fixed asap. > > > > I didn't touch them yet because I first like to get the IT on our CI box > working again. > > > > LieGrue, > > strub > > > > > > --- On Sun, 7/31/11, Stephen Connolly <stephen.alan.conno...@gmail.com> > wrote: > > > >> From: Stephen Connolly <stephen.alan.conno...@gmail.com> > >> Subject: Re: Random errors in parallely executed tests > >> To: "Maven Developers List" <dev@maven.apache.org> > >> Date: Sunday, July 31, 2011, 6:28 PM > >> the buildhelper goal is for when you > >> are launching jetty/etc from the pom. > >> or when you need to filter the port into on disk > >> resources. > >> > >> if launching within the test case, just assign it to port > >> 0. a request for > >> port 0 is a request for an unused port in the top 16k (or > >> depending on the > >> os, anywhere above 1024). then you ask the connector what > >> port it bound to. > >> > >> - Stephen > >> > >> --- > >> Sent from my Android phone, so random spelling mistakes, > >> random nonsense > >> words and other nonsense are a direct result of using swype > >> to type on the > >> screen > >> On 31 Jul 2011 18:40, "Benson Margulies" <bimargul...@gmail.com> > >> wrote: > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > >
