1

I am currently implementing a new Maven Plugin and I would like to use Java 11 for compilation and execution.

However, I would like my Maven plugin to be used by most of our projects. Some of them are running in Java 8, some in Java 11.

Is it mandatory to use Java 8 in my Maven Plugin if I want it to be included in other project ? Is there a way to implement it in Java 11 and make it available for Java 8 project ?

fabien7474
  • 16,300
  • 22
  • 96
  • 124
  • If eventually, you plan to create artifacts using a JAR created out of your classes it doesn't really matter, you can develop them in either Java-8 or Java-11(MR-JAR). The difference might be when someone exposes them as JMODs instead which were introduced in Java-9 and not much work on Maven had reflected upon wrapping such a type. – Naman Jan 17 '20 at 09:18
  • *"Is there a way to implement it in Java 11 and make it available for Java 8 project ?"* No. You can use the Java 11 compiler, although it's much easier to use the Java 8 compiler to ensure compatibility (fewer compiler options needed), but the source code still has to be Java 8 code, i.e. no use of Java 9+ features or APIs. – Andreas Jan 17 '20 at 09:18

1 Answers1

2

As quite often: it depends. And with Maven Java is used at different levels, so this requires a bit of explanation:

Are you going to use Java 9+ specific features/APIs?

If not, you can build your project with Java 11, but you need to add <release>8</release> to the maven-compiler-plugin to ensure the code is Java 8 compatible.

If you do plan to use Java 9+ features/APIs, add <release>11</release> to the maven-compiler-plugin. Now you require your users that they run Maven with at least Java 11 (which is not a problem, even Maven 3.0 runs fine with Java 14-ea).

Even though Maven runs on Java 11, your users can still create Java 8 compatible projects (just like the "if not, ..." from the first bullet), but most are used to run and build with Java 8.

Robert Scholte
  • 11,889
  • 2
  • 35
  • 44