maven-compiler-plugin VS Feign

The configuration enablePreview exists since version 3.10.1 of the Maven Compiler Plugin. So in general I recommend to use the most recent versions of the plugins otherwise it might happen that some configuration options or alike might not exist at all or special things for newer JDK versions.

Once you have built and debugged your first simple plugin, check out how mainstream/official plugins are built (you can find them on GitHub) and experiment. It really takes a week to get going, maybe less, that's it.

The Maven Compiler Plugin uses JDK 8 and compiles only 3 source files. This is different from the 5 source files compiled in the Java 17 version.

Like, check out how the compiler plugin itself is tested: https://github.com/apache/maven-compiler-plugin/blob/master/pom.xml#L254

A new, Feign client, to make the get request to https://example.com/themes. This client will expose a get() method.

The actual project for feign is OpenFeign https://github.com/OpenFeign/feign . Spring comes with it's own starter . Add below dependency to the project

Find a community/project that interests you, I've gone with feign. Head on into the issues tab, and you'll see all the potential contributions you could make. Starting out, it's a good idea to search for tags like "bug", or "good first issue".

Feign has support for what you're looking for. https://github.com/OpenFeign/feign/tree/master/jaxrs2

feign-spring4 gives you a type safe client proxy of an interface annotated with Spring MVC annotations.

At the risk of doxxing myself, I'm a contributer attempting to fix this issue with this pr. The project has existed for a while now, and since I'm not part of the openfeign team, so the final solution they end up using isn't up to me. So there's technical debt to deal with (how the project is built and tested currently) and whether or not multi-release jars are the best solution in this case.