Add maven relocation

[paul-dingemans]

Description

Add maven relocation block to ktlint-cli and ktlint-cli-reporter-baseline

When publishing to the local Maven repository, a 0.51.0-FINAL version of the pom.xml is created for the modules above. The modules contain the expected content. But the pom.xml is missing the signature. Another side effect is that the 1.0.1-SNAPSHOT version of the modules above is not created anymore as the signing block is now added to the module.

In 1.0.0 more modules have been relocated. They need to be added as well when it is clear how this should be approached.

Checklist

Before submitting the PR, please check following (checks which are not relevant may be ignored):

• Commit message are well written. In addition to a short title, the commit message also explain why a change is made.
• At least one commit message contains a reference Closes #<xxx> or Fixes #<xxx> (replace<xxx> with issue number)
• Tests are added
• KtLint format has been applied on source code itself and violations are fixed
• CHANGELOG.md is updated
• PR description added

Documentation is updated. See difference between snapshot and release documentation

• Snapshot documentation in case documentation is to be released together with a code change
• Release documentation in case documentation is related to a released version of ktlint and has to be published as soon as the change is merged to master
• In case of adding a new rule, it needs to be added to experimental rules documentation

[paul-dingemans]

@Goooler Can you please help me out with this change? I have sent a slack message a while ago with more details.

[Goooler]

Not be familiar with maven relocation, but if you wan't to sign this, could add something like:

signing {
    sign(publishing.publications["relocation-ktlint-cli-reporter-baseline"])
}

Ref:

ktlint/build-logic/src/main/kotlin/ktlint-publication.gradle.kts

Line 90 in ea8df7e

sign(publishing.publications["maven"])

[paul-dingemans]

My question is not specifically about the maven relocation, but how to avoid code duplication in Gradle build. I have now added a publication and signing block in each module for which the maven coordinate has been changed. It is good enough as it will be removed soon.

[Goooler]

And if this is only for maven coordinate relocation, can we rebase this PR to 0.51.0-FINAL branch and publish it, instead of on the master.

[paul-dingemans]

And if this is only for maven coordinate relocation, can we rebase this PR to 0.51.0-FINAL branch and publish it, instead of on the master.

I don't know how to create a release from a branch. I might not have enough privileges for that. I have tested on my local machine that publish to maven local creates both artifacts for 0.51.0-FINAL and 1.0.1. Only downside is that I have to remove the changes of this PR after publication of the next release.