-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolving relative refs broken with Spring Boot 3.2 #2080
Comments
Hi @david0 , I have came accross same problem for my project ,it is working with Springboot 3.1 but getting same error with SB version 3.2 onwards. Have you found any workaround to solve this issue? Thanks, |
Yes, as a workaround you can set the loaderImplementation back to CLASSIC: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.2-Release-Notes#nested-jar-support |
I have tried that CLASSIC loader using spring-boot-maven-plugin, but when I checked generated manifest file in jar , it still uses new jar launcher loader class. |
I have modified plugin slightly , just kept configuration tag before execution tag. It works for me.
Any update from swagger parser team when they will fix this issue? |
Parsing schemas with refs to other files fails with the following exception, when the jar file is run:
I'm using Spring Boot 3.2.x which has a nested jar and the loader has been re-written in Spring Boot 3.2: Spring Boot 3.2 Release Notes: Nested Jar Support.
This seems to break the OpenAPI Parsers way of resolving $refs.
Small project to repoduce the problem can be found here: david0/swagger-parser-spring3.2-issue2080
Don't forget to run the jar and not via IDE to reproduce the problem.
The text was updated successfully, but these errors were encountered: