Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Check Spotless formatting by default build #45

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

Copy link
Member

@slachiewicz slachiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this not the default?

Copy link
Member

@slawekjaranowski slawekjaranowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be done in parent pom.
please look at Maven parent.

@ascheman
Copy link
Author

ascheman commented Mar 19, 2025

If it was active by default, the GH action builds of the mentioned projects should have failed, right?
The parent POM uses the check in a particular profile (format-check), which is activated when the CI environment variable is set.

Should I change the PR to set this environment variable or perhaps to activate the Maven profile?

@slachiewicz
Copy link
Member

So to rephrase, yes it should be done on parent in similar way that we have in maven parent pom for apache org, where we agreed that always format code, not only check.

@ascheman ascheman force-pushed the feature/spotless-check branch from 4728227 to 0e3e406 Compare April 8, 2025 09:45
@ascheman ascheman force-pushed the feature/spotless-check branch from 0e3e406 to 2381261 Compare April 8, 2025 10:09
@ascheman
Copy link
Author

ascheman commented Apr 8, 2025

I switched to setting the CI environment variable.

@ascheman ascheman marked this pull request as ready for review April 8, 2025 10:11
Comment on lines +77 to +79
env:
CI: true

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ascheman added a commit to support-and-care/plexus-pom that referenced this pull request Apr 8, 2025
Builds should either apply spotless or check for it
depending on whether it is running in CI or not.

Detected in the course of support-and-care/maven-support-and-care#77 and codehaus-plexus/.github#45
@ascheman
Copy link
Author

ascheman commented Apr 8, 2025

Replaced by codehaus-plexus/plexus-pom#344

@ascheman ascheman closed this Apr 8, 2025
slachiewicz pushed a commit to codehaus-plexus/plexus-pom that referenced this pull request Apr 8, 2025
Builds should either apply spotless or check for it
depending on whether it is running in CI or not.

Detected in the course of support-and-care/maven-support-and-care#77 and codehaus-plexus/.github#45
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.

3 participants