Skip to content

[issues-100] - Fix the Spotless Maven plugin configuration#101

Draft
fabiobrz wants to merge 2 commits intoIntersmash:mainfrom
fabiobrz:fix.spotless
Draft

[issues-100] - Fix the Spotless Maven plugin configuration#101
fabiobrz wants to merge 2 commits intoIntersmash:mainfrom
fabiobrz:fix.spotless

Conversation

@fabiobrz
Copy link
Copy Markdown
Member

Description

Resolves #100

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Checklist

  • Code contributed by me aligns with current project license: Apache 2.0
  • Pull Request contains a description of the changes
  • Pull Request does not include fixes for multiple issues/topics
  • Code is self-descriptive and/or documented
  • I have implemented unit tests to cover my changes
  • N/A I tested my code in OpenShift - just code formatting configuration

@fabiobrz fabiobrz changed the title Fix.spotless Fix the Spotless Maven plugin configuration Mar 23, 2026
@fabiobrz fabiobrz changed the title Fix the Spotless Maven plugin configuration [issues-87] - Fix the Spotless Maven plugin configuration Mar 23, 2026
@fabiobrz fabiobrz changed the title [issues-87] - Fix the Spotless Maven plugin configuration [issues-100] - Fix the Spotless Maven plugin configuration Mar 23, 2026
@fabiobrz
Copy link
Copy Markdown
Member Author

Thinking a bit more about this, the reason for skipping the applications sources is that actually there can be cases where them might carry license headers as well.
We need some kind of mechanism to prevent Spotless from adding the license header to such files.

@fabiobrz fabiobrz marked this pull request as draft March 25, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The Spotless plugin configuration only applies to the "application-provider" module

1 participant