Bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3.10.0

[dependabot]

Bumps com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3.10.0.

Release notes

Sourced from com.diffplug.spotless:spotless-maven-plugin's releases.

Maven Plugin v3.10.0

Added

• New <shortenFullyQualifiedTypes> step for Java, which replaces fully-qualified type names with their simple names and adds the imports they need. Best combined with <importOrder> and <removeUnusedImports>. (#2945)
• Add embedded lockfiles to Eclipse JDT for every supported version (4.9 through 4.40), so eclipse() resolves from Maven Central instead of querying a P2 update site. Versions without an embedded lockfile still fall back to P2 provisioning. (#1996)
• Add support to apply alternate license header within same format (#872)
• Add support to skip license header application based on source file content pattern (#650).

Fixed

• removeUnusedImports no longer fails on Java import module declarations. (#2890)
• Concurrent P2 provisioning no longer races Solstice's on-disk cache (affects Eclipse-based formatters under parallel builds). (#3004)

Changes

• Default google-java-format remains 1.28.0 on JVM 17; bumps to 1.30.0 on JVM 21+; require at least 1.30.0 on JVM 25+ for import module support.
• Bump default eclipse version to latest 4.39 -> 4.40. (#1996)
• Document Maven skip properties spotless.skip, spotless.check.skip, and spotless.apply.skip. Goal-specific skips now live on their own mojos so they no longer leak across goals. (#3009)
• Bump default adocfmt version 0.2.0 -> 0.3.1, which adds table formatting support (<formatTables>, <tableLayout>, <tableMaxLineWidth>, <tableBlankLines>).

Commits

• 426b21d Published maven/3.10.0
• 2fd42ea Published gradle/8.10.0
• d71ed1a Published lib/4.10.0
• 8b57c01 Add shortenFullyQualifiedTypes step (fixes #2945) (#3005 closes #2945)
• 6b42c5e fix: make the FQN-collecting visitor a named static class
• 4430823 Better organization on the changelogs.
• 45bea6d Better place to put the shortenFullyQualifiedTypes docs
• 0c49e65 chore: spotlessApply
• 1c5bc0a docs: list the Java import steps in the plugin README tables of contents
• cd57b58 docs: document shortenFullyQualifiedTypes in the plugin READMEs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

Mend Scan Results

Status: ✅ No findings detected

SCA scan output

Identified 20 dependencies

Detected 0 vulnerabilities (0 Critical, 0 High, 0 Medium, 0 Low)





No Policy violations were detected

Project 'project-sources-maven-plugin' was updated, for more information, visit the Mend platform: https://ibmets.whitesourcesoftware.com/app/orgs/Enterprise%20Applications/applications/summary?project=405ebdd8-b5fb-40ee-a916-a52d73f8cf58
Or the Core UI: https://ibmets.whitesourcesoftware.com/Wss/WSS.html#!project;token=b8088a2b4f1545d88d5660329158e3ef701ee33470df4be98cec5ff6df6d8d09

Mend AI scan succeeded.

Support Token: 087e82fa769b545f2af1eca068694284b1787605877778

SAST scan output

*no findings*

Full logs and artifacts