Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Yes, I agree. Created https://issues.apache.org/jira/browse/MNG-7913 On Tue, Oct 17, 2023 at 4:31 PM Konrad Windszus wrote: > I think we should revise the decision to not backport > https://issues.apache.org/jira/projects/MNG/issues/MNG-7587 < >

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

I think we should revise the decision to not backport https://issues.apache.org/jira/projects/MNG/issues/MNG-7587 to Maven 3.9.x… > On 16. Oct 2023, at 22:08, Garret Wilson wrote: > > On 10/16/2023 4:59 PM,

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

On 10/16/2023 4:59 PM, Tamás Cservenák wrote: You'd use Plexus? In 2023? I don't know what I'd use. I'm asking. I haven't written a Maven plugin yet. I'm just reading the latest documentation, and the [Plugin Developers Centre](https://maven.apache.org/plugin-developers/) seems to say at

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

You'd use Plexus? In 2023? Please no :) TL;DR: Plexus shim (used in Maven, more specifically https://github.com/eclipse/sisu.plexus) builds atop of sisu.inject project, so the same thing applies. In other words: whatever is "managed by sisu, should be max Java 14" bytecode in current release

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

On 10/16/2023 4:36 PM, Tamás Cservenák wrote: … no, this applies to "sisu managed components" ONLY. So not ALL the code needs to be downgraded, only those annotated with JSR330 annotations. After reading and trying to understand https://maven.apache.org/maven-jsr330.html , does this mean

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Tamás, thank you very much for the clarification. The previous announcement sounded like it applied to every Maven plugin. Garret On 10/16/2023 4:36 PM, Tamás Cservenák wrote: Hej Garret, no, this applies to "sisu managed components" ONLY. So not ALL the code needs to be downgraded, only

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Hej Garret, no, this applies to "sisu managed components" ONLY. So not ALL the code needs to be downgraded, only those annotated with JSR330 annotations. And yes, Maven 3.9.6 could upgrade Sisu to the latest version, basically lifting this limitation. HTH T On Mon, Oct 16, 2023 at 9:19 PM

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Wait, really? I have an annotation processor being developed now with Java 17, and parts of it soon will need to move to a Maven plugin. This means that I'll have to downgrade all the code to Java 14?? In 2023? Are there any workarounds? The issue #94 you mentioned has already been closed as

Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Howdy, This mail is just a general response (initiated by those asking me in private): it seems that the Maven team "forgot" to emphasize an important question on the Maven site, while it is becoming more and more pressing, especially as Java 17 is out long time ago, and Java 21 is here as well.