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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1322:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Component report should be refactored to provide both a Maven and an Ant task
> -----------------------------------------------------------------------------
>
>                 Key: TAP5-1322
>                 URL: https://issues.apache.org/jira/browse/TAP5-1322
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>              Labels: bulk-close-candidate
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)