Open paul58914080 opened 2 months ago
Hi @paul58914080,
I'm not yet sure what the exact problem is. However, the Spring Boot 3.2 migration guide mentions "Nested Jar Support" ^1, which looks like it relates to your problem.
Also, they state:
If you do find issues with the new implementation, however, we have provided a fallback option that will allow you to use the old code.
Are you sure this is a problem in Camunda, or could it also be a problem in Spring Boot? 🤔
For Gradle, you can use the following to fall back to the old behavior:
bootJar {
loaderImplementation = org.springframework.boot.loader.tools.LoaderImplementation.CLASSIC
}
I'll have a close look to this problem soon. Stay tuned!
Best; Tassilo
With classic loader it does work fine
bootJar {
loaderImplementation = org.springframework.boot.loader.tools.LoaderImplementation.CLASSIC
}
I'll wait for your further investigation.
Hi @paul58914080,
We would be able to fix this by adding these lines of code:
// Required for Spring Boot 3.2 Nested Jar Support
// https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.2-Release-Notes#nested-jar-support
if (urlPath.startsWith("nested:")) {
urlPath = urlPath.substring(7);
}
We should also add tests to ensure that this works as expected. I think a Spring Boot integration test would make sense.
Here we have already some special application setups where we could add another one: https://github.com/camunda/camunda-bpm-platform/tree/master/spring-boot-starter/starter-qa
Would you have time to contribute this?
Best, Tassilo
Hi @paul58914080,
Friendly reminder to answer my question. 🙂
Best, Tassilo
Environment (Required on creation)
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
I am using a multi-module project![image](https://github.com/camunda/camunda-bpm-platform/assets/10730990/83f620f9-8a45-49bb-bd18-61cab755a3ae)
Fails to boot with the following exception:
Steps to reproduce (Required on creation)
Use the following link and follow the readme instructions
https://github.com/paul58914080/cammunda-sample-issue
Observed Behavior (Required on creation)
Unable to boot
Expected behavior (Required on creation)
Should be able to boot
Root Cause (Required on prioritization)
Solution Ideas
Hints
What I observed is, for spring-boot v 3.1.x it used to find process.xml with
jar:file
and it works !With spring-boot 3.2.x it fails with
jar:nested
Links
Dev2QA handover