[xwiki-notifications] [Issue] Assigned: (XWIKI-2169) Automatic logging of deprecated method calls in Velocity

[Sergiu Dumitriu (JIRA)]

     [ http://jira.xwiki.org/jira/browse/XWIKI-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergiu Dumitriu reassigned XWIKI-2169:
--------------------------------------

    Assignee: Sergiu Dumitriu

> Automatic logging of deprecated method calls in Velocity
> --------------------------------------------------------
>
>                 Key: XWIKI-2169
>                 URL: http://jira.xwiki.org/jira/browse/XWIKI-2169
>             Project: XWiki Core
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.3 RC1
>            Reporter: Sergiu Dumitriu
>         Assigned To: Sergiu Dumitriu
>            Priority: Minor
>             Fix For: Future
>
>
> We should automatically log calls to deprecated methods from velocity. This will allow early fix of the code, as it is otherwise hard to maintain velocity code up to date until things stop working.
> This can be done in three ways:
> - put LOG.warn messages in the deprecated methods
> - use a custom uberspector that checks for @Deprecated annotations on each method called
> - use an aspect that inserts these calls for each deprecated method
> The first solution is the worst, as it pollutes the code too much, and makes it hard to maintain and keep track of deprecated methods. So the choice is between an uberspector and an aspect. The uberspector seems better, as it allows checking all the method calls, even from other packages than our own. And given that we'll split the platform in even more components, it will be awkward to run and maintain the aspect in each module.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.xwiki.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira