-
Notifications
You must be signed in to change notification settings - Fork 0
Configure Spotless through common convention plugins #25
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
Conversation
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR migrates from the Spotless plugin to a centralized Stream conventions plugin (version 0.3.0), consolidating code formatting, license management, and Maven publishing configuration. This refactoring removes local configuration in favor of convention-based setup.
Key changes:
- Upgraded
streamConventionsfrom 0.2.0 to 0.3.0 and addedstream-projectplugin - Removed Spotless plugin and migrated formatting configuration to
streamProjectextension - Removed local license template files and license generation tasks
Reviewed Changes
Copilot reviewed 2 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| gradle/libs.versions.toml | Updated streamConventions version, added stream-project plugin, removed spotless plugin, fixed trailing space formatting |
| config/license/license.template | Removed license template file (moved to conventions plugin) |
| config/license/generated/license-2025.txt | Removed generated license file (moved to conventions plugin) |
| config/license/generated/license-2024.txt | Removed generated license file (moved to conventions plugin) |
| build.gradle.kts | Removed Spotless configuration, license generation tasks, and Maven publish configuration; added streamProject configuration block |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@aleksandar-apostolov I'm not applying formatting here to avoid having all changes in the PR transitioning to the plugins. We can force merge this one and then merge the follow up: #26 |
|



Goal
AND-880
As the title says.
Note: I'm not running
spotlessApplyhere to avoid bundling the migration with all the Spotless changes. I'll do it in a follow up (#26). What will change:Implementation
Replace local Spotless configuration with the convention.
Testing
Run spotlessApply and verify that the files are updated accordingly.
Checklist