[ 
https://issues.apache.org/jira/browse/CAMEL-23213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet updated CAMEL-23213:
------------------------------------
    Description: 
The ExportTest in camel-jbang-core fails on JDK 17 with:

{code}
UnsupportedClassVersionError: 
org/apache/camel/springboot/catalog/SpringBootRuntimeProvider has been compiled 
by a more recent version of the Java Runtime (class file version 65.0), this 
version of the Java Runtime only recognizes class file versions up to 61.0
{code}

The camel-catalog-provider-springboot 4.19.0-SNAPSHOT artifact from the 
camel-spring-boot repo is compiled with Java 21 target (class file version 
65.0), making it incompatible with JDK 17.

This is a *pre-existing, widespread issue* affecting multiple PRs whose 
incremental CI pulls in camel-jbang-core on JDK 17 runners. Confirmed on PRs 
for CAMEL-23209 (SMB), CAMEL-23212 (Docling), CAMEL-23210 (PQC), and others.

20 out of 66 ExportTest tests fail (all Spring Boot runtime type variants). JDK 
21 and 25 are unaffected.

The fix needs to happen in the camel-spring-boot repo — either the catalog 
provider should be compiled with Java 17 target, or the ExportTest should 
handle the class version mismatch gracefully (e.g. skip Spring Boot tests when 
running on JDK 17).

  was:
The ExportTest.testShouldGenerateProjectMultivalue test in camel-jbang-core 
fails on JDK 17 with:

{code}
UnsupportedClassVersionError: 
org/apache/camel/springboot/catalog/SpringBootRuntimeProvider has been compiled 
by a more recent version of the Java Runtime (class file version 65.0), this 
version of the Java Runtime only recognizes class file versions up to 61.0
{code}

The camel-catalog-provider-springboot 4.19.0-SNAPSHOT artifact from the 
camel-spring-boot repo is compiled with Java 21 target (class file version 
65.0), making it incompatible with JDK 17.

This affects CI when the incremental build pulls in camel-jbang-core on JDK 17 
runners.

The test downloads camel-catalog-provider-springboot at the current snapshot 
version via CatalogLoader and tries to load SpringBootRuntimeProvider via 
reflection, which fails on JDK 17.


> ExportTest fails on JDK 17 due to camel-catalog-provider-springboot compiled 
> with Java 21 target
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23213
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23213
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.19.0
>
>
> The ExportTest in camel-jbang-core fails on JDK 17 with:
> {code}
> UnsupportedClassVersionError: 
> org/apache/camel/springboot/catalog/SpringBootRuntimeProvider has been 
> compiled by a more recent version of the Java Runtime (class file version 
> 65.0), this version of the Java Runtime only recognizes class file versions 
> up to 61.0
> {code}
> The camel-catalog-provider-springboot 4.19.0-SNAPSHOT artifact from the 
> camel-spring-boot repo is compiled with Java 21 target (class file version 
> 65.0), making it incompatible with JDK 17.
> This is a *pre-existing, widespread issue* affecting multiple PRs whose 
> incremental CI pulls in camel-jbang-core on JDK 17 runners. Confirmed on PRs 
> for CAMEL-23209 (SMB), CAMEL-23212 (Docling), CAMEL-23210 (PQC), and others.
> 20 out of 66 ExportTest tests fail (all Spring Boot runtime type variants). 
> JDK 21 and 25 are unaffected.
> The fix needs to happen in the camel-spring-boot repo — either the catalog 
> provider should be compiled with Java 17 target, or the ExportTest should 
> handle the class version mismatch gracefully (e.g. skip Spring Boot tests 
> when running on JDK 17).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to