update the xsl stylesheets and try out a source, shell

jetty-documentation/pom.xml

@@ -132,7 +132,8 @@
           <dependency>
             <groupId>net.sf.docbook</groupId>
             <artifactId>docbook-xml</artifactId>
-            <version>5.0-all</version>
+            <!--version>5.0-all</version-->
+            <version>5.1b4-all</version>
             <classifier>resources</classifier>
             <type>zip</type>
             <scope>runtime</scope>

jetty-documentation/src/main/asciidoc/quick-start/getting-started/jetty-running.adoc

@@ -19,6 +19,7 @@
 
 To start Jetty on the default port of 8080, run the following command:
 
+[source, shell]
 ....
 > cd $JETTY_HOME
 > java -jar start.jar
@@ -40,6 +41,7 @@ Instead, see how to link:#creating-jetty-base[create a Jetty Base] below.
 
 Within the standard jetty distribution there is the `demo-base` directory, which demonstrates the recommended way to run Jetty in a directory separately from $JETTY_HOME:
 
+[source, shell]
 ....
 > cd $JETTY_HOME/demo-base/
 > java -jar $JETTY_HOME/start.jar
@@ -75,6 +77,7 @@ ____
 
 You can see the configuration of the demo-base by using the following commands:
 
+[source, shell]
 ....
 > cd $JETTY_HOME/demo-base/
 > java -jar $JETTY_HOME/start.jar --list-modules
@@ -97,6 +100,7 @@ jetty.base::
 
 The `jetty.home` and `jetty.base` properties may be explicitly set on the command line, or they can be inferred from the environment if used with commands like:
 
+[source, shell]
 ....
 > cd $JETTY_BASE
 > java -jar $JETTY_HOME/start.jar
@@ -104,6 +108,7 @@ The `jetty.home` and `jetty.base` properties may be explicitly set on the comman
 
 The following commands: create a new base directory; enables a HTTP connector and the web application deployer; copies a demo webapp to be deployed:
 
+[source, shell]
 ....
 > JETTY_BASE=/tmp/mybase
 > mkdir $JETTY_BASE
@@ -140,6 +145,7 @@ INFO: Base directory was modified
 
 You can configure Jetty to run on a different port by setting the `jetty.http.port` Property on the command line:
 
+[source, shell]
 ....
 > cd $JETTY_BASE
 > java -jar $JETTY_HOME/start.jar jetty.http.port=8081
@@ -151,13 +157,15 @@ By default, the jetty distribution defines the jetty.http.port property in the `
 
 ____
 [NOTE]
+--
 The configuration by properties works via the following chain:
-+
+
 * The start.d/http.ini file is part of the effective command line and contains the --module=http argument which activates the http module.
 * The modules/http.mod file defines the http module which specifies the etc/jetty-http.xml configuration file and the template ini properties it uses.
 * The jetty.http.port property is used by the Property XML element in etc/jetty.http.xml to inject the ServerConnector instance with the port.
-+
+
 For more information see the link:#quickstart-config[Quickstart Configuration Guide] and link:#configuring-connectors[Configuring Connectors].
+--
 ____
 
 [[quickstart-starting-https]]
@@ -165,6 +173,7 @@ ____
 
 To add the HTTPS connector to a jetty configuration, the https module can be activated by the following command:
 
+[source, shell]
 ....
 > java -jar $JETTY_HOME/start.jar --add-to-startd=https,http2
 [...]
@@ -192,6 +201,7 @@ ____
 
 You can configure the SSL connector to run on a different port by setting the `jetty.ssl.port` property on the command line:
 
+[source, shell]
 ....
 > cd $JETTY_BASE
 > java -jar $JETTY_HOME/start.jar jetty.ssl.port=8444
@@ -206,6 +216,7 @@ If you used --add-to-start command, then you can edit this property in the start
 The job of the `start.jar` is to interpret the command line, `start.ini` and `start.d` to build a Java classpath and list of properties and configuration files to pass to the main class of the Jetty XML configuration mechanism. 
 The `start.jar` mechanism has many options which are documented in the xref:startup[] administration section and you can see them in summary by using the command:
 
+[source, shell]
 ....
 > java -jar $JETTY_HOME/start.jar --help
 ....