Type: Feature Request
Status: Closed (View Workflow)
Affects Version/s: 2.1.2
Fix Version/s: 2.2.0
Similar Issues:Show 10 results
MPJDOCBOOK-78 <injections> should work (release version must not be hardcoded in the docbook master.xml's) MPJDOCBOOK-50 Perform entity injections on XIncluded sources as well MPJDOCBOOK-60 the output wrongly be generated into the target/docbook/docbook/publish directory MPJDOCBOOK-51 Allow dynamic DTD entity injection more generally MPJDOCBOOK-81 net.sf.docbook docbook 1.74.0 does not exist or canot be referenced MPJDOCBOOK-48 have jDocBook resolve docbook dtd references locally MPJDOCBOOK-83 NPE when no injections configured MPJDOCBOOK-80 The docbook version configured shouldn't have to be magic version that is in sync with the xsl's and dependencies. It should support a newer version too. MPJDOCBOOK-55 jdocbook plugin: "today" entity is expanded using default system locale MPJDOCBOOK-19 Allow specifying/providing fonts
Wanted to let you know that I am experimenting with adding support for this in trunk (-> 2.2.0).
There are 2 options in play here:
1) <options><applyStandardInjectionEntities>true</applyStandardInjectionEntities></options> (true is the default). Makes some "standard" information available to your docbook source in the form of DTD entities. Currently there are just 2: (1) "version" which is the defined version from pom; (2) "today" which is a new Date() formatted as "MMMM d yyyy"
</value></entity></entities> would again make available a DTD entity named "version" available to your docbook as a DTD entity with the value of your pom-defined version.
I think this should allow coverage of most cases.