You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/01/26 12:25:39 UTC

[GitHub] [maven-plugin-tools] cstamas edited a comment on pull request #46: [MPLUGIN-378] Group extractors and improve their selection, deprecate javadoc extractor

cstamas edited a comment on pull request #46:
URL: https://github.com/apache/maven-plugin-tools/pull/46#issuecomment-1022150314


   > Is there no way to detect `@Deprecated` instead of introducing our own `#isDeprecated()`?
   
   You mean to detect is extractor deprecated? If so, then why complicate? I mean, we author extractor API, and we author extractor implementations and we decide which one is deprecated... we could do some fancy classcheck/reflection on injected component instance, that would break in a moment (not that we plan) we switch to AOP Guice, as then we get proxies injected, and so on and so on.... why not just keep it simple?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org