You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Laird Nelson <lj...@gmail.com> on 2024/10/24 22:02:55 UTC
maven-compiler-plugin 3.13.0, testCompile and JDK 23
I'm using maven-compiler-plugin 3.13.0, which is the latest non-beta
release as of this writing.
I'm using toolchains. I have a JDK 23 set up.
I have a module-info.java.
The compile goal works fine (my code is compiled successfully using my
toolchain's JDK 23).
The testCompile goal fails, indicating that a classfile version of 67 (JDK
23's) cannot be handled by the compiler plugin. This occurs when the plugin
attempts to use ASM via plexus-languages to read my module-info.class (that
it itself generated, incidentally).
This sort of issue has happened in Mavenland before, with prior Java
upgrades. I wonder if a test in the Maven codebase for this situation
should be added.
Best,
Laird
Re: maven-compiler-plugin 3.13.0, testCompile and JDK 23
Posted by Laird Nelson <lj...@gmail.com>.
OK. Adding an explicit <dependency> on plexus-java 1.3.0 fixed the issue
(maven-compiler-plugin 3.13.0 uses 1.2.0), probably because plexus-java
1.3.0 uses a later version of ASM as you say.
On Thu, Oct 24, 2024 at 6:13 PM Olivier Lamy <ol...@apache.org> wrote:
> Well, TBH, the ASM upgrade is the usual/famous pain with any JDK new
> version :), and this happens for every project that depends on it.
> I was blocked testing Jetty build with jdk24 til the last asm 9.7.1
> except not depending on ASM not sure what to do.
>
> On Fri, 25 Oct 2024 at 08:04, Laird Nelson <lj...@gmail.com> wrote:
> >
> > I'm using maven-compiler-plugin 3.13.0, which is the latest non-beta
> > release as of this writing.
> >
> > I'm using toolchains. I have a JDK 23 set up.
> >
> > I have a module-info.java.
> >
> > The compile goal works fine (my code is compiled successfully using my
> > toolchain's JDK 23).
> >
> > The testCompile goal fails, indicating that a classfile version of 67
> (JDK
> > 23's) cannot be handled by the compiler plugin. This occurs when the
> plugin
> > attempts to use ASM via plexus-languages to read my module-info.class
> (that
> > it itself generated, incidentally).
> >
> > This sort of issue has happened in Mavenland before, with prior Java
> > upgrades. I wonder if a test in the Maven codebase for this situation
> > should be added.
> >
> > Best,
> > Laird
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven-compiler-plugin 3.13.0, testCompile and JDK 23
Posted by Olivier Lamy <ol...@apache.org>.
Well, TBH, the ASM upgrade is the usual/famous pain with any JDK new
version :), and this happens for every project that depends on it.
I was blocked testing Jetty build with jdk24 til the last asm 9.7.1
except not depending on ASM not sure what to do.
On Fri, 25 Oct 2024 at 08:04, Laird Nelson <lj...@gmail.com> wrote:
>
> I'm using maven-compiler-plugin 3.13.0, which is the latest non-beta
> release as of this writing.
>
> I'm using toolchains. I have a JDK 23 set up.
>
> I have a module-info.java.
>
> The compile goal works fine (my code is compiled successfully using my
> toolchain's JDK 23).
>
> The testCompile goal fails, indicating that a classfile version of 67 (JDK
> 23's) cannot be handled by the compiler plugin. This occurs when the plugin
> attempts to use ASM via plexus-languages to read my module-info.class (that
> it itself generated, incidentally).
>
> This sort of issue has happened in Mavenland before, with prior Java
> upgrades. I wonder if a test in the Maven codebase for this situation
> should be added.
>
> Best,
> Laird
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org