You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/08/27 23:18:58 UTC

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

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

Howard M. Lewis Ship closed TAP5-1322.
--------------------------------------

    Resolution: Invalid

This is no longer relevant since the introduction of the JavaDoc doclet for Tapestry.

> 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)