romani commented on issue #18: [MCHECKSTYLE-381] remove call to checker.setClassLoader(). URL: https://github.com/apache/maven-checkstyle-plugin/pull/18#issuecomment-568715301 > Maybe you might want to use semantic versioning It is not that easy in our almost 20 years old project. Details: https://checkstyle.org/#Development_Cycle https://github.com/checkstyle/checkstyle/issues/3709 > and a more stable API with transition times API is too big, bunch of very very old decisions based on lack of time many years ago ..... . We do try to break API one by one. This API change is so long awaited, I started to warn about its removal probably about 5 years ago. But till it stop to compile or work .... nobody care. > Please don't interpret the feedback as criticism thanks for confirmation, and I do not misinterpretate it, It completely natural for plugins to live close to core library, and it will be much better for plugin .... but we are not ready to change playground of project .... if it goes forward ... let it go for now as it is. > Probably your team could treat it as additional integration test coverage to run the maven-checkstyle-plugin with -Prun-its? we do not run this ... BUT we heavily depend on maven plugin to keep functional regression (huge amount of execution of plugin in different projects) on leash. If we are introducing breaking changes for plugin, we get to know this from CI when PR is created to checkstyle project. That is why we would like some changes to be more released more frequently as we can not remove code till maven plugin is migrated off it. > might strengthening the communication between the checkstyle and Maven teams improve the situation? We are always open to help, just mention us in PR and we will help to resolve migrations to new version of checkstyle or any other core library questions.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
