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" <[email protected]> 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 <[email protected]> wrote: > >> From: Stephen Connolly <[email protected]> >> Subject: Re: Random errors in parallely executed tests >> To: "Maven Developers List" <[email protected]> >> 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" <[email protected]> >> wrote: >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
