activate missing check goal of maven-spotless-plugin

[Pankraz76]

See JENKINS-XXXXX.

Testing done

Proposed changelog entries

• human-readable text

Proposed changelog category

/label

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[github-actions]

Missing required label for changelog. Requires at least 1 of: bug, developer, dependencies, internal, localization, major-bug, major-rfe, rfe, regression-fix, removed, skip-changelog. Found: .

You can add the required label by adding a comment with the following text: /label <category>

[Pankraz76]

applying spotless changes everything this has to be done once or the config needs to be aligned with check. Its only possible because spotless is not activated by default...

[Pankraz76]

https://github.com/apache/maven-parent/blob/d41c7679f9efc780d4b36820067ba6205b2ef9c7/pom.xml#L1408

https://github.com/apache/maven-parent/blob/d41c7679f9efc780d4b36820067ba6205b2ef9c7/pom.xml#L1419

[Pankraz76]

https://github.com/checkstyle/checkstyle/blob/c3cfac2b5bff84aa13a73dd6ec19b64b0dad7bdc/pom.xml#L1490

[Pankraz76]

• Improve Developer Experience pmd/pmd#5875

@oowekyala
@adangel

consider this as positive and negative example. They need to apply spotless once then they can use it. or fix the config just like in PMD....

[Pankraz76]

So the issue is caused when moving the plugin to the pluginManagement section as the checkstyle and as expected.

This changed the config somehow and then the entire project.

Having applied spotless myself i know this could not be. When there is spotless there is out of sync possible.