On Thu, Aug 24, 2017 at 11:19 AM, Robert Munteanu <romb...@apache.org> wrote: > ...I am not familiar with the reasons for using port 8888, but would it be > worth dropping this port and using 8080 from now on?...
+1 for using a single port throughout. I see a few more occurences than you mention but nothing major, see below. -Bertrand ./contrib/launchpad/testing/pom.xml: <jetty.http.port>8888</jetty.http.port> ./contrib/launchpad/testing/README.txt:with mvn jetty:run, from http://localhost:8888/system/console/vmstat. *** ./launchpad/builder/README.txt: http://localhost:8888 ./launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/JsonRenderingTest.java: // We skip http://localhost:8888/org.apache.sling.launchpad.testing-6-SNAPSHOT/ ./launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/JsonRenderingTest.java: // or http://localhost:8888/ ./samples/installing-dependencies/pom.xml: <slingUrl>http://localhost:8888/system/console</slingUrl> ./testing/tools/src/main/java/org/apache/sling/testing/tools/junit/RemoteLogDumper.java: baseUrl = "http://localhost:8888";;
