You're right, i read the issue as if it was fixed so that Groovy classes
could not be used as components and not the other way around.
And issue 2425 looks good also for Groovy support.
Thanks.
Tobias Wehrum wrote:
Why should fixing the bug "Groovy classes can no longer be used as
component cl
Why should fixing the bug "Groovy classes can no longer be used as
component classes because of the public metaClass field" make it harder
to work with Groovy and Tapestry?
Anyway... maybe https://issues.apache.org/jira/browse/TAPESTRY-2425 ?
Hugo Palma schrieb:
The news item for 5.0.13 state
