-
Notifications
You must be signed in to change notification settings - Fork 411
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
refactor: 1348 upgrade to spring boot 3x #1504
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
using new `jakarta` namespace
Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
the previously uses package springdoc-openapi-ui was not the correct one to be used with spring-boot 3 the application properties 'springdoc.packages-to-scan' and 'springdoc.pathsToMatch' are now needed for the OpenAPI specs to be generated properly.
as the springfox-swagger package was replaced, this workaround is not needed anymore. - optimize imports
as we currently only expose the v2 API we don't need the grouped OpenAPI specs. Once we want to generate both v2 and v3 API specs in parallel we need to reintroduce this.
the SpecVersion used here should be the OpenAPI V30 which is already the default for an OpenAPI instance and is therefore removed.
name change due to specs being OpenAPI 3 now instead of swagger 2
debugging the exact location of errors was not straight forward, due to messages containing the wrong location. Added Hint on how to debug in docstring. Adjusted size numbers after removal of centrality endpoint.
due to the 'schedule_duration' and 'walking_time' being of type Duration, the type of the parameters was exposed as objects. The values passed were however always Strings. - Adjusted schema type in RouteRequest to String for durations
as the exact number of tags, paths and components will change and for components is not consistent, we just check if there are some at all.
springboot 3 requires jakarta servlet 6 which in turn requires tomcat 10: https://tomcat.apache.org/whichversion.html
TheGreatRefrigerator
force-pushed
the
chore/1348-upgrade-to-spring-boot-3x
branch
from
July 21, 2023 14:37
d38be18
to
61523f7
Compare
changed some more of the pattern variables, see |
MichaelsJP
approved these changes
Jul 24, 2023
MichaelsJP
approved these changes
Jul 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
have been resolved.
[Unreleased] heading.
along with a short description of what it is for, and documented this in the Pull Request (below).
(at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
importer etc.), I have generated longer distance routes for the affected profiles with different options
(avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
points generated from the current live ORS.
If there are differences then the reasoning for these MUST be documented in the pull request.
and why the change was needed.
Fixes # .
Information about the changes
As there were quite some refactorings done, this is not just a chore but refactor PR
Examples and reasons for differences between live ORS routes, and those generated from this pull request
Required changes to ors config (if applicable)