[TAP5-1322] Component report should be refactored to provide both a Maven and an Ant task

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 5.2
• Component/s: tapestry-component-report
• Labels: bulk-close-candidate
• Assignee: Unassigned
• Reporter: Howard Lewis Ship
• Created: 22/Oct/10 23:10
• Updated: 27/Aug/14 21:17
• Resolved: 27/Aug/14 21:17

Description

Currently, building the component documentation is totally linked to Maven, which is not fair to every other build system out there.

It seems like there should be two parts; some code that generates the report, constructing a set of .xdoc files, and hooks for Ant or Maven to execute that code.

In the Ant world, you would probably then use XSLT to transform the .xdoc files to a final output format.