Is there a way to set Language level? I want to use jep467 under jdk17

[potoo0]

Just like Jetbrains IDEA.

idea Rendered jep467 Markdown Comment under jdk17:

vscode-java behavior:

[rgrunber]

Are you actually able to compile or run any code in this setup ? Or are you just using this approach to get the markdown comments. As far as I know, any attempt to build a project with source compliance larger than the target environment results in something like :

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.14.0:compile (default-compile) on project
my-app: Fatal error compiling: error: specified target release 17 is too old for the specified source release 23
[ERROR]   --release 17 is recommended when compiling code to run on JDK 17

[datho7561]

I've set up a project like this:

This is what I get when I go to run the project:

[potoo0]

@rgrunber @datho7561
em... Works well for me.

env:

• idea: 2024.3.5
• idea remote development, hosted wsl2
• gradle 8.13

[datho7561]

@rgrunber is it possible to enable hover documentation for Markdown regardless of the compiler version? I think it's helpful to provide even if it doesn't translate into "real" javadoc when you build the javadoc site. It's not like the Markdown comments are invalid under Java 17.

@potoo0 I'm pretty sure it's not possible to compile Java 23 code with a Java 17 compiler. I tried playing around with the project setup in intellij, and tried switching to the Intellij JDK from Temurin, but neither of those things helped.

I've been using Intellij's built-in project system, but it seems you are using Gradle. Maybe Gradle is launched with Java 17 but then uses a Java 23 compiler to compile the code? The Gradle toolchain documentation seems to indicate that you can specify a version of Java to use to compile your code, and it will automatically detect an installed JDK or download a JDK for you and build your project with that.

[potoo0]

@rgrunber is it possible to enable hover documentation for Markdown regardless of the compiler version? I think it's helpful to provide even if it doesn't translate into "real" javadoc when you build the javadoc site. It's not like the Markdown comments are invalid under Java 17.

@datho7561
It seems that idea's project language will not affect the doc's hover.

see .idea/misc.xml in gradle-demo.tar.gz

[potoo0]

Are you actually able to compile or run any code in this setup ? Or are you just using this approach to get the markdown comments. As far as I know, any attempt to build a project with source compliance larger than the target environment results in something like :

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.14.0:compile (default-compile) on project
my-app: Fatal error compiling: error: specified target release 17 is too old for the specified source release 23
[ERROR]   --release 17 is recommended when compiling code to run on JDK 17

I just want markdown comments, is it possible to apply jep-467 only for render markdown comments without being limited by project language level?

[rgrunber]

I think this would be an upstream issue to consider. I'm pretty sure the state of the AST model is determined by the compiler compliance settings. In other words, by setting the language level to < 23, we already affect what the AST will contain. For example, https://github.com/eclipse-jdt/eclipse.jdt.core/blob/6f9e882af58e22f6c7b017a94203e7290ab2621a/org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/DocCommentParser.java#L82-L84 .

[xiaoxiyao]

@potoo0 I also want to use markdown comments in lower versions of Java. Do you have any solutions?