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/09/03 20:03:57 UTC
[jira] Moved: (TAP5-839) Tapestry should ignore (public) synthetic
methods in module classes
[ https://issues.apache.org/jira/browse/TAP5-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship moved TAPESTRY-2746 to TAP5-839:
-----------------------------------------------------
Component/s: (was: tapestry-ioc)
Issue Type: Bug (was: Improvement)
Affects Version/s: (was: 5.1.0.0)
Key: TAP5-839 (was: TAPESTRY-2746)
Project: Tapestry 5 (was: Tapestry)
> Tapestry should ignore (public) synthetic methods in module classes
> -------------------------------------------------------------------
>
> Key: TAP5-839
> URL: https://issues.apache.org/jira/browse/TAP5-839
> Project: Tapestry 5
> Issue Type: Bug
> Reporter: Peter Niederwieser
>
> Groovy (and probably other alternative languages as well) enriches its classes with public synthetic methods. For module classes written in Groovy, Tapestry complains that it doesn't recognize these methods. Because synthetic methods are obviously not meant for Tapestry, they should be ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.