rmannibucau commented on PR #765: URL: https://github.com/apache/maven/pull/765#issuecomment-1182330757
Hi, Am I missing something or this PR makes any plugin not *compiled* with api >= 3.1.0 as deprecated? Is it true? AFAIK if you use maven 2 and the same surfacing API than with 3.1 then you don't want this warning so it sounds to me that to implement this feature you should find another implementation path to avoid too much false positives. One option can be to use the API signature and visit the plugin bytecode and check it uses deprecated/deleted API, this will be slower but at least the user reporting will be accurate cause right now it faces the end user with warning he can't do anything about - and worse being that the plugin developpers willing to do that will imply warnings on user side. What about using this slower but more accurate implementation in `versions-maven-plugin`? It is clearly the place it belongs to since this is not a check you want for each build but when you manage your versions *only* IMHO. Hope it makes sense. -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
