docbkx-tools: Testing DocBook XSL 1.77.0

DocBook XSL 1.77.0 has been out for a couple of weeks. I have not found anything unexpected, yet.

ForgeRock core docs have three layers to build between the stylesheets and the docs that use forgerock-doc-maven-plugin. Here is what I did in order to enable testing:

1. Get the DocBook Maven project, https://docbook.svn.sourceforge.net/svnroot/docbook/trunk/maven, update the versions to pull the latest stylesheets, and mvn install a local copy.

   $ svn diff
   Index: docbook-xsl/pom.xml
   ===================================================================
   --- docbook-xsl/pom.xml	(revision 9386)
   +++ docbook-xsl/pom.xml	(working copy)
   @@ -5,7 +5,7 @@
      <artifactId>docbook-xsl</artifactId>
      <name>DocBook XSL Stylesheets</name>
      <packaging>pom</packaging>
   -  <version>1.76.1</version>
   +  <version>1.77.0</version>
      <description>These are XSL stylesheets for transforming DocBook XML document instances into various output formats.
      </description>
      <url>http://sourceforge.net/projects/docbook/</url>
   @@ -18,8 +18,8 @@
   
      <properties>
   -    <docbook.xsl.release>docbook-xsl-1.76.1</docbook.xsl.release>
   -    <docbook.xslns.release>docbook-xsl-ns-1.76.1</docbook.xslns.release>
   +    <docbook.xsl.release>docbook-xsl-1.77.0</docbook.xsl.release>
   +    <docbook.xslns.release>docbook-xsl-ns-1.77.0</docbook.xslns.release>
      </properties>
   
      <build>

2. Get docbkx-tools, http://docbkx-tools.googlecode.com/svn/trunk, update the stylesheet version, and mvn install a local copy.

   $ svn diff
   Index: docbkx-maven-plugin/pom.xml
   ===================================================================
   --- docbkx-maven-plugin/pom.xml	(revision 258)
   +++ docbkx-maven-plugin/pom.xml	(working copy)
   @@ -62,7 +62,7 @@
        <dependency>
          <groupId>net.sf.docbook</groupId>
          <artifactId>docbook-xsl</artifactId>
   -      <version>1.76.1</version>
   +      <version>1.77.0</version>
          <type>zip</type>
          <classifier>ns-resources</classifier>
        </dependency>

3. Get forgerock-doc-maven-plugin, https://svn.forgerock.org/commons/forgerock-doc-maven-plugin/trunk, update the docbkx-tools version, and mvn install a local copy.
   Update: Thanks to Chris Ridd. Also need to change AbstractBuildMojo.java as shown.

   $ svn diff
   Index: src/main/java/org/forgerock/doc/maven/AbstractBuildMojo.java
   ===================================================================
   --- src/main/java/org/forgerock/doc/maven/AbstractBuildMojo.java	(revision 311)
   +++ src/main/java/org/forgerock/doc/maven/AbstractBuildMojo.java	(working copy)
   @@ -32,7 +32,7 @@
         * Docbkx Tools plugin version to use. Executions seem to hit an NPE when
         * the version is not specified.
         *
   -     * @parameter default-value="2.0.14" expression="${docbkxVersion}
   +     * @parameter default-value="2.0.15-SNAPSHOT" expression="${docbkxVersion}
         * @required
         */
        private String docbkxVersion;
   Index: pom.xml
   ===================================================================
   --- pom.xml	(revision 312)
   +++ pom.xml	(working copy)
   @@ -61,7 +61,7 @@
     </licenses>
   
     <properties>
   -  <docbkxVersion>2.0.14</docbkxVersion>
   +  <docbkxVersion>2.0.15-SNAPSHOT</docbkxVersion>
      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
      <maven.compiler.target>1.6</maven.compiler.target>
      <maven.compiler.source>1.6</maven.compiler.source>

4. Use your local Maven installation to build your test documentation.