Merge pull request #102 from OpenLiberty/qa

Merge qa to master: fixed the hotspots

Author: gkwan-ibm

README.adoc

@@ -72,7 +72,7 @@ contains a [hotspot]`pom.xml` file, which defines the project configuration, dep
 and so on.
 
 Navigate to the `start` directory where your [hotspot]`pom.xml` file is located. Your `pom.xml` file
-is configured to include the [hotspot=193-215]`liberty-maven-plugin`, which allows
+is configured to include the [hotspot=168-190]`liberty-maven-plugin`, which allows
 you to install applications into Open Liberty as well as manage the server instances.
 
 pom.xml
@@ -221,8 +221,8 @@ updates the running server without the need for the server to be restarted.
 
 Take a look at your [hotspot file=0]`pom.xml` file.
 
-The loose application support is enabled with the [hotspot=206 file=0]`<looseApplication/>`
-element in the [hotspot=193-215 file=0]`liberty-maven-plugin` plug-in.
+The loose application support is enabled with the [hotspot=181 file=0]`<looseApplication/>`
+element in the [hotspot=168-190 file=0]`liberty-maven-plugin` plug-in.
 
 pom.xml
 [source, XML, linenums, role="code_column"]
@@ -406,23 +406,23 @@ Open Liberty supports a number of different server packages. The sample applicat
 currently generates a `usr` package that contains the servers and application to be
 extracted onto an Open Liberty installation.
 
-The type of server package is configured with [hotspot=33 file=0]`<packaging.type/>` in
+The type of server package is configured with [hotspot=32 file=0]`<packaging.type/>` in
 the [hotspot file=0]`pom.xml`.
 
 Instead of creating a server package, you can generate a runnable JAR file that contains
 the application along with a server runtime. This JAR can then be run anywhere and deploy
 your application and server at the same time. To generate a runnable JAR, invoke the
-[hotspot=40-48 file=0]`runnable-package` profile by using the `-P` flag:
+[hotspot=39-47 file=0]`runnable-package` profile by using the `-P` flag:
 
 [role='command']
 ```
 mvn install -P runnable-package
 ```
 
 The `-P` flag specifies the Maven profile to be run during the build. In this case, the
-[hotspot=40-48 file=0]`runnable-package` profile is invoked, which temporarily overrides
-the [hotspot=33 hotspot=46 file=0]`packaging.type` property from the `usr` package to the `runnable`
-package. This property then propagates to the [hotspot=193-215 file=0]`liberty-maven-plugin`
+[hotspot=39-47 file=0]`runnable-package` profile is invoked, which temporarily overrides
+the [hotspot=32 hotspot=45 file=0]`packaging.type` property from the `usr` package to the `runnable`
+package. This property then propagates to the [hotspot=168-190 file=0]`liberty-maven-plugin`
 plug-in, which generates the server package that you want.
 
 When the build completes, you can find the runnable `getting-started.jar` file in the
@@ -431,15 +431,15 @@ Open Liberty, including the entirety of Java EE and MicroProfile. As a result, t
 is over 100 MB. To omit the features that you don't need and package the JAR with only
 the [hotspot=2-9 file=1]`features` that you defined in the [hotspot file=1]`server.xml` file, use
 `minifiy,runnable` as the packaging type. To build a minimal runnable JAR, invoke the
-[hotspot=49-57 file=0]`minify-runnable-package` profile by using the `-P` flag:
+[hotspot=48-56 file=0]`minify-runnable-package` profile by using the `-P` flag:
 
 [role='command']
 ```
 mvn install -P minify-runnable-package
 ```
 
-The [hotspot=49-57 file=0]`minify-runnable-package` profile overrides the
-[hotspot=33 hotspot=55 file=0]`packaging.type` property from the `usr` package to the `minify,runnable`
+The [hotspot=48-56 file=0]`minify-runnable-package` profile overrides the
+[hotspot=32 hotspot=54 file=0]`packaging.type` property from the `usr` package to the `minify,runnable`
 package and generates a runnable JAR file that contains only the [hotspot=2-9 file=1]`features` that you
 explicitly enabled in your [hotspot file=1]`server.xml` file. As a result, the
 generated JAR is only about 50 MB.