> The Markdown route involves more pain in getting to successful scripts to > building to documentation deliverable artifacts. The upsides are in ease of > authoring and reading the source of the documentation.
It's fairly commonplace for projects of non-trivial size and complexity to develop their own tooling to meet the needs of build and other ancillary matters. Developing a markdown maven plugin seems fairly straightforward, although I must admit PDF generation sounds daunting. I personally think PDF documentation is borderline worthless, but I can appreciate opinions to the contrary. In any case development of tooling to meet our needs seems perfectly justifiable. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
