Align code style and quality checks across Allure Java - #1274
Merged
Conversation
pratushnyi
approved these changes
May 14, 2026
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
2 participants
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.
Context
This PR refreshes the project’s code style and quality configuration to make formatting and static analysis more consistent across the Allure Java codebase. There are no intended user-facing behavior changes; the goal is to keep the library easier to maintain and safer to evolve.
Java formatting now follows a shared Eclipse formatter and import order, while Scala and Groovy sources are formatted through Spotless as well. Quality checks were tightened for main sources, generated code is handled more cleanly, and import restrictions were added.
Checklist