search

greglarsen / docbkx-tools

Automatically exported from code.google.com/p/docbkx-tools
0 stars 1 forks source link

Add olink support #36

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
olink allows cross-document linking.

I think there are 2 phases:
- modify the plugin in order to allow targetsFilename (*.target.db) to be
specified when multiples docbook sources are proceeded within a single
maven execution
- create a mojo in order to generate the targetDatabaseDocument file

@see
http://groups.google.com/group/docbkx-tools-users/browse_thread/thread/252f0ca5a
02b2590

Original issue reported on code.google.com by MimilO...@gmail.com on 8 May 2009 at 11:01

GoogleCodeExporter commented 8 years ago 
The workaround mentioned in the thread works best for smaller projects, as it 
results in 1 <execution> per file, per format.

This morning I implemented olinking for a docset with 7 books that each output 
single-page HTML, and also 1 HTML chunk per chapter. So far I've only done the 
olinks for single-page HTML. That results in 107 more lines in the POM. ( See 
http://sources.forgerock.org/viewrep/openam/trunk/opensso/openam-site/pom.xml?r=
1471 )

I for one would be very please to see docbkx-tools handle the target databases 
without my help. :-)

Original comment by mark.cr...@gmail.com on 25 Nov 2011 at 12:56

GoogleCodeExporter commented 8 years ago 
If you're doing olinks today and wondering about automation, I've moved this 
out to a Maven plugin that wraps docbkx-tools and drives it with mojo-executor.

The methods at 
https://github.com/markcraig/forgerock-doc-maven-plugin/blob/master/src/main/jav
a/org/forgerock/doc/maven/PreSiteBuildMojo.java#L297 and 
https://github.com/markcraig/forgerock-doc-maven-plugin/blob/master/src/main/jav
a/org/forgerock/doc/maven/PreSiteBuildMojo.java#L369 build the target DB.

Original comment by mark.cr...@forgerock.com on 28 Jun 2012 at 7:40