The purpose of the jDocBook Plugin is to allow these DocBook transformations to occur as a natural part of the users Maven build. The main difficulty with this has always been the fact that DocBook transformations are usually very closely tied to the user's local environment. The design goal with writing this plugin was to utilize Maven's dependency mechanism to bring all the pieces together on demand. Those pieces are:
These are the ingredients that when mixed with the source file(s) and stirred with an XSLT transformer produce the desired output(s). Currently, only SAXON is supported as the transformer factory. I have had issues getting XALAN to work properly.
|
Goals Overview
|
The jDocBook Plugin defines a dedicated project packaging ("jdocbook"). In part, this packaging is used to redefine a suitable set of lifecycle phases pertinent to performing DocBook transformations. Below are the defined lifecycle phases, with the goals attached to them:
|
Usage
|
Detailed usage instructions for the jDocBook Plugin can be found here. |
Examples
|
To provide you with better understanding of some usages of the jDocBook Plugin, you can take a look at the following examples: |