rfscholte commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-416623370 The Java Release Train comes with a lot of challenges, whereas staying in line with ASM is a clear example. I understand there are projects that want to experiment with new ASM features, but that might imply extra codechanges. (a request for having an option to get the latest ASP api version was declined) Is it important to have a released version of the plugin? Otherwise you can fork the plugin yourself and implement this yourself. Another option I'm thinking of is to introduce an interface, so required changes from ASM can be implemented by anybody, then it will be a matter of adding this dependency to the plugin in your own pom. maven-plugin-plugin is just one of the plugins, there are more plugins suffering with the same issue and I don't expect that we will do releases on demand, our team is just too small and the project too big. I'm open for any solution that won't require a new release of this plugin with every change (new API) of ASM
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
