[
https://issues.apache.org/jira/browse/CAMEL-22697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron Fitzwater updated CAMEL-22697:
--------------------------------------
Description:
When having openjdk-17 installed locally....
It appears that having either of these (the latter being documented) in
application.properties:
camel.jbang.java-version=17
camel.jbang.javaVersion=17
... and then running (quarkus specific):
{code:java}
camel run * --fresh --runtime=quarkus --quarkus-version=3.20.1 --observe{code}
fails with:
{code:java}
Running using Quarkus v3.20.1 (preparing and downloading files)
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.14.1:compile (default-compile)
on project CamelJBang: Fatal error compiling: error: release version 21 not
supported -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException {code}
An export does produce a pom with, correctly:
{code:java}
<maven.compiler.release>17</maven.compiler.release>{code}
... so export does take it into account (and is documented here:
[https://camel.apache.org/manual/camel-jbang.html#_configuring_exporting]
Installing openjdk-21 locally appears to let the run command to success, but
being that both 17,21 are supported, and being that 21 is the default, it seems
there should be a way to set this?
was:
When having openjdk-17 installed locally....
It appears that having either of these (the latter being documented) in
application.properties:
camel.jbang.java-version=17
camel.jbang.javaVersion=17
... and then running:
{code:java}
camel run * --fresh --runtime=quarkus --quarkus-version=3.20.1 --observe{code}
fails with:
{code:java}
Running using Quarkus v3.20.1 (preparing and downloading files)
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.14.1:compile (default-compile)
on project CamelJBang: Fatal error compiling: error: release version 21 not
supported -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException {code}
An export does produce a pom with, correctly:
{code:java}
<maven.compiler.release>17</maven.compiler.release>{code}
... so export does take it into account (and is documented here:
https://camel.apache.org/manual/camel-jbang.html#_configuring_exporting
Installing openjdk-21 locally appears to let the run command to success, but
being that both 17,21 are supported, and being that 21 is the default, it seems
there should be a way to set this?
> camel-jbang: javaVersion not working with camel run / quarkus
> -------------------------------------------------------------
>
> Key: CAMEL-22697
> URL: https://issues.apache.org/jira/browse/CAMEL-22697
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Cameron Fitzwater
> Priority: Major
>
> When having openjdk-17 installed locally....
>
> It appears that having either of these (the latter being documented) in
> application.properties:
> camel.jbang.java-version=17
> camel.jbang.javaVersion=17
>
> ... and then running (quarkus specific):
> {code:java}
> camel run * --fresh --runtime=quarkus --quarkus-version=3.20.1 --observe{code}
> fails with:
> {code:java}
> Running using Quarkus v3.20.1 (preparing and downloading files)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.14.1:compile
> (default-compile) on project CamelJBang: Fatal error compiling: error:
> release version 21 not supported -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException {code}
> An export does produce a pom with, correctly:
> {code:java}
> <maven.compiler.release>17</maven.compiler.release>{code}
> ... so export does take it into account (and is documented here:
> [https://camel.apache.org/manual/camel-jbang.html#_configuring_exporting]
> Installing openjdk-21 locally appears to let the run command to success, but
> being that both 17,21 are supported, and being that 21 is the default, it
> seems there should be a way to set this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
