On 20 Sep 2010, at 16:21, Felix Meschberger wrote: > Hi all, > > We currently have an inconsistency in the setup of the jetty:run > configuration in the the launchpad/builder module and the default port > used by the Sling standalone application. > > The jetty plugin is configured to use port 8888 by default, while the > standalone application by default uses port 8080. In addition the > integration tests in the launchpad/integration-tests module also assume > a default of port 8888. > > I think we should consolidate on a single port number. > > Since most configuration uses 8888 by default, the easiest would > probably be to change the standalone app default to 8888. > > WDYT ?
I am not certain this is a good idea. At the moment you can run an app, and do another build at the same time without touching the config or adding a -p on the command line. Having the test run on 8888 is good in that respect. Most people expect java http apps to appear on 8080. Having to communicate to a wider community that they need to add -p 8080 or stop going to 8080 and now go to 8888 is going to generate list traffic of confused downstream users. Ian > > Regards > Felix