You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/04/22 22:03:47 UTC
[jira] Created: (TAP5-662) Component documentation should identify
the events that may be triggered by a component
Component documentation should identify the events that may be triggered by a component
---------------------------------------------------------------------------------------
Key: TAP5-662
URL: https://issues.apache.org/jira/browse/TAP5-662
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.1.0.4
Reporter: Howard M. Lewis Ship
This has been done informally in the past as just JavaDoc. It would be nice if the events that can be published by a component be statically defined (via a special annotation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-662) Component documentation should identify
the events that may be triggered by a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-662:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Component documentation should identify the events that may be triggered by a component
> ---------------------------------------------------------------------------------------
>
> Key: TAP5-662
> URL: https://issues.apache.org/jira/browse/TAP5-662
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> This has been done informally in the past as just JavaDoc. It would be nice if the events that can be published by a component be statically defined (via a special annotation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-662) Component documentation should identify
the events that may be triggered by a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-662.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.4
> Component documentation should identify the events that may be triggered by a component
> ---------------------------------------------------------------------------------------
>
> Key: TAP5-662
> URL: https://issues.apache.org/jira/browse/TAP5-662
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.4
>
>
> This has been done informally in the past as just JavaDoc. It would be nice if the events that can be published by a component be statically defined (via a special annotation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-662) Component documentation should identify
the events that may be triggered by a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-662.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.4
> Component documentation should identify the events that may be triggered by a component
> ---------------------------------------------------------------------------------------
>
> Key: TAP5-662
> URL: https://issues.apache.org/jira/browse/TAP5-662
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.4
>
>
> This has been done informally in the past as just JavaDoc. It would be nice if the events that can be published by a component be statically defined (via a special annotation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-662) Component documentation should identify
the events that may be triggered by a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-662:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Component documentation should identify the events that may be triggered by a component
> ---------------------------------------------------------------------------------------
>
> Key: TAP5-662
> URL: https://issues.apache.org/jira/browse/TAP5-662
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> This has been done informally in the past as just JavaDoc. It would be nice if the events that can be published by a component be statically defined (via a special annotation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.