Use Docbkx Maven Plugin to build handbook

[knutsiem]

Here is a suggestion for simplifying handbook building using Docbkx Maven Plugin instead of manually applying DocBook XSLs with Ant. To the best of my knowledge, the documents produced remain unchanged.

A few related observations:

• Wouldn't packaging "pom" be better for handbook than "jar"?
• highlight.xsl does not seem to be in use? Should it be deleted?
• identity.xsl and generate-id.xsl seem to be of limited value. If the point is to generate sensible and stable anchor names then I think just hand-coding them would be better. If not, then why not rely on the anchors generated by DocBook? Am I missing something?

[trygvis]

Hm, it looks good and the PDF seems to look the same but I am wondering what is the real upside with the change?

• "pom" packaging might make more sense
• highlight.xml can be removed
• The identity xsl can be removed if it's not used anymore. The comments explain what it was used for.
• I'm not sure about generate-id.xsl, I made it for a reason but can't recall it now. It can probably be removed.

[knutsiem]

It's just a matter of preferring a working Maven plugin over delegating to a very "manual" Ant build. I can understand that this does not seem to bring a lot of immediate value, but as I said when I opened the request: I see this as a build simplification, and I mean that in an objective sense. If you disagree I would love to hear why. Naturally, it's your call entirely.