Format the converted site page to the project's spotless rules - #488
Merged
slachiewicz merged 1 commit intoAug 6, 2026
Merged
Conversation
The APT to Markdown conversion indented paragraph continuations inside list items with four spaces; spotless wants two, so a build of master fails its own spotless:check. Formatting only: the rendered page is unchanged.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The APT to Markdown conversion indented paragraph continuations inside list items with four spaces; spotless wants two, so a build of
mastercurrently fails its ownspotless:check.Formatting only, produced by
mvn spotless:apply. Verified by building the site before and after: the rendered page is unchanged.Follow-up to #487, part of the migration tracked in apache/maven-doxia-converter#139