You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Chris Lewis (JIRA)" <de...@tapestry.apache.org> on 2007/12/28 12:24:43 UTC
[jira] Created: (TAPESTRY-2000) Enable @Mixins annotation in
component classes
Enable @Mixins annotation in component classes
----------------------------------------------
Key: TAPESTRY-2000
URL: https://issues.apache.org/jira/browse/TAPESTRY-2000
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0
Reporter: Chris Lewis
Priority: Minor
Fix For: 5.0.8
Implementation mixins can be declared in component classes using the @Mixin annotation for each desired mixin. If I have 4 such mixins in a component I will have 4 @Mixin annotations, each of course paired with a @SuppressWarnings("unused") annotation to shut eclipse up. It would be nice if I could just use the already existing @Mixins annotation once to list all mixins. Of course the semantics would be a bit different - perhaps it would need to be on the component class instead of a field in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2000) Enable @Mixins annotation in
component classes
Posted by "Chris Lewis (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556311#action_12556311 ]
Chris Lewis commented on TAPESTRY-2000:
---------------------------------------
Noted - sorry about that.
> Enable @Mixins annotation in component classes
> ----------------------------------------------
>
> Key: TAPESTRY-2000
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2000
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Chris Lewis
> Priority: Minor
>
> Implementation mixins can be declared in component classes using the @Mixin annotation for each desired mixin. If I have 4 such mixins in a component I will have 4 @Mixin annotations, each of course paired with a @SuppressWarnings("unused") annotation to shut eclipse up. It would be nice if I could just use the already existing @Mixins annotation once to list all mixins. Of course the semantics would be a bit different - perhaps it would need to be on the component class instead of a field in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org