build: Updated PlantUML dependency to 1.2025.0 #32
Conversation
This file contains hidden or 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
…irement. Removed download code from build.sbt and added PlantUML as regular dependency.
…rget platform to Java 1.8.
…rget platform to Java 1.8.
…build due to misisng dependencies.
Oliver-Loeffler
commented
Feb 4, 2025
| } | ||
| } getOrElse NotFound | ||
| } getOrElse NotFound() |
There was a problem hiding this comment.
This was proposed by SBT.
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.
Hello there,
thank you for providing this great add-on for Gitbucket. Unfortunately I've encountered a few .puml files which could not be rendered with PlantUML 1.2022.5 but with later 1.2024. versions. This version is prrovided by plugin version 1.7.0.
So I've decided to see, if I can provide an update in form of a PR.
This PR includes:
Interestingly PlantUML changed the SVG character encoding from UTF-8 to u-sascii.
I would greatly appreciate if you would be able to review this proposal. Please advice if you see need for rework.
My proposal for this is to call it version 1.8.0.
Thank you!