Correct content output from the console
┏━━━━━ Debug [area.list] ━━━
┣ SQL: select * from area WHERE parent_code=? and name like concat('%',?,'%')
┣ 参数: [0, 山北]
┣ 位置: jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
┣ 时间: 2ms
┣ 结果: [0]
┗━━━━━ Debug [area.list] ━━━
Expected behavior
The build folder of the project is target
Java8 compilation -parameter parameters are in effect
Screenshots
If applicable, add screenshots to help explain your problem.
Output from "Gradle for Java"
[debug] [gradle-server] Starting server
[debug] [gradle-server] Gradle Server cmd: c:\Users\Administrator.vscode\extensions\vscjava.vscode-gradle-3.12.7\lib\gradle-server.bat 56950
[info] [gradle-server] Server started, listening on 56950
[info] Gradle client connected to server
[debug] Refreshing tasks
[info] Java Home: D:\dragonwell-17
[info] JVM Args: --add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=384m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=UTF-8,-Duser.country=CN,-Duser.language=zh,-Duser.variant
[info] Gradle User Home: D:\gradle-repository
[info] Gradle Version: 8.3
[info] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
Extension Name: vscode-gradle Extension Version: 3.12.7 OS Version: win10 VSCode version: 1.81.0
Describe the bug build.gradle configuration buildDir and compileJava, but don't
To Reproduce
maven, java17, gradle8.3 are local installation directories
Expected behavior The build folder of the project is target Java8 compilation -parameter parameters are in effect
Screenshots If applicable, add screenshots to help explain your problem.
Output from "Gradle for Java" [debug] [gradle-server] Starting server [debug] [gradle-server] Gradle Server cmd: c:\Users\Administrator.vscode\extensions\vscjava.vscode-gradle-3.12.7\lib\gradle-server.bat 56950 [info] [gradle-server] Server started, listening on 56950 [info] Gradle client connected to server [debug] Refreshing tasks [info] Java Home: D:\dragonwell-17 [info] JVM Args: --add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=384m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=UTF-8,-Duser.country=CN,-Duser.language=zh,-Duser.variant [info] Gradle User Home: D:\gradle-repository [info] Gradle Version: 8.3 [info] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
CONFIGURE SUCCESSFUL in 15s [info] Found 187 tasks
Does the bug still exist if you disable all other extensions? Yes
Additional context Add any other context about the problem here.