Add relocation info to maven (if we think this is needed)

[klaraward]

See https://maven.apache.org/guides/mini/guide-relocation.html

[malaporte]

I'm not sure if the steps highlighted in that doc are required? We do not need to republish the older versions to the new group ID, right? Can't you just publish a new one using Spotify's?

[klaraward]

I'm not sure if the steps highlighted in that doc are required? We do not need to republish the older versions to the new group ID, right? Can't you just publish a new one using Spotify's?

Looking in to how this works.

[klaraward]

I think we do something like this: https://stackoverflow.com/questions/24494974/how-do-i-deploy-a-relocation-pom-xml-to-sonatypes-oss-repository
Which would mean someone who can sign and deploy for the com.coveogroupId needs to do it (aka @malaporte)

[klaraward]

Also the docs from the description say

[](https://maven.apache.org/guides/mini/guide-relocation.html#releasing-the-next-version)Releasing the next version
When the next release of foo is made, you should publish two Maven 2 POM files: first you should publish foo's POM with the new groupId org.bar.

Because data in the repository is not supposed to change, Maven doesn't download POM files that it has already downloaded. Therefore you will also need to publish a relocation POM file with the old groupId bar for the new version: this should be a minimal relocation POM (as described in step 4 above), but for the new version of foo.

For the release after that, you only need to publish a Maven POM with a groupId of org.bar, since users of the previous version have been informed of the changed groupId.

So from what I understand:

1. Bump the version and publish a release with the com.spotify.fmt groupId (aka org.bar in the example above) (Someone with access to the spotify groupId and signing, aka @klaraward (me) should do that) - Change groupId and package to com.spotify.fmt #124 covers those changes
2. Keep the same version and publish a relocation POM where the groupId is com.coveo (aka bar) and the relocation groupId is com.spotify.fmt (Someone with access to the coveo groupId and signing, aka @malaporte should do that) - Change to pom for this is in [Don't merge] Add relocation info from com.coveo to com.spotify.fmt #130

Does that sound reasonable?

[klaraward]

It looks to me that this could be done any time after a new release with the new spotify groupId, so I wont consider the relocation fix blocking that release.

[malaporte]

OK just tell me when the release is done on your side and I'll try to follow the steps mentioned.