FWIW, Nigel is correct that the port allocator is most helpful if it's used across a set of projects, but he's incorrect that it is only helpful in that circumstance. The Port Allocator plugin starts at a suitably high port so that it avoids the typical ports uses - 8080, 8888, 9090, etc. java.net seems to be having one of it's typical outages, so I can't validate the port range used.
Justin -----Original Message----- From: Bertrand Delacretaz [mailto:[email protected]] Sent: Tuesday, October 13, 2009 5:32 AM To: [email protected] Subject: Re: [jira] Commented: (SLING-920) Hudson continuous integration setup On Tue, Oct 13, 2009 at 11:27 AM, Felix Meschberger <[email protected]> wrote: > ...Just wild thinking -- can we setup the integration tests using > standalone sling without using cargo ?... Yes, that's been on my mind for a while as that would make test setup faster probably as well. Didn't get to doing it yet, and looks like I won't have time to work on this in the next few weeks. Don't hesitate to make any changes as long as all tests pass ;-) > ...This would problably enable us to > somehow communicate the port number used by Sling to the outside > trying to call into Sling ?... You mean letting Sling select a port dynamically, and letting the tests know which port it is? Why not, or write small Maven plugin to find an available port, there are several options. -Bertrand
