Michael Osipov

I'll get back to this next week.

> > Reference: [apache/maven-checkstyle-plugin#136 (comment)](https://github.com/apache/maven-checkstyle-plugin/pull/136#issuecomment-2152517655) > > java.lang.NoSuchMethodError: > > This is a runtime issue. Other thread said compile compatibility is what was being looked for. > > This also...

Although I will provide an elaborated answer next week. All I wanted is to provide to as many users (like @motlin) as possible Maven Core plugins with a reasonable set...

Guys, how to move forward with this? While I understand your sentiments, your limitations seems very arbitrary and biased to me. I try to include as many users as possible...

I am currently looking into option 3 with the given limitation put aside.

Draft: https://github.com/apache/maven-checkstyle-plugin/pull/143. Requires availability in Maven Central though.

> > Note that I do not know what the technical motivation was to move Java 11 for Checkstyle. > > You can read the discussion at #9146 . Basically...

> There's a part of this conversation I don't understand. If I'm on a project where I want/need to use an old version of Java (like Java 8), I must...

> > there is zero mentioning about the technical benefits of 11, not to speak of 17. > > There was none. It was more about "keeping up with the...

> We are small team, I try to not put more work on our team, we barely able to handle activities and support for main repo. So backport exists for...