[
https://issues.apache.org/jira/browse/VELOCITY-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891803#comment-17891803
]
Roel Pieters commented on VELOCITY-985:
---------------------------------------
Just tested with 2.4.1 and all's well with the world for us.
> Add legacy method for behaviour before VELOCITY-952
> ---------------------------------------------------
>
> Key: VELOCITY-985
> URL: https://issues.apache.org/jira/browse/VELOCITY-985
> Project: Velocity
> Issue Type: Wish
> Components: Engine
> Affects Versions: 2.4
> Reporter: Roel Pieters
> Priority: Minor
>
> With an upgrade to 2.4 we run into the problem that findMethod now returns
> the topmost method. We annotate overridden methods and check the annotations
> in our own UberSpectimpl to open them up for use in our platform and with the
> change from VELOCITY-152 this fails because we always get the topmost method.
> It would help us a lot if there was a way to keep the old behaviour. Maybe
> I'm missing something simple and it's still possible. If that's the case
> could you point us in te right direction?
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
