Closed klaraward closed 1 year ago
Did you create this for example? I don't think we need. If we want to republish each old version with our group we need them to checkout each version tag and republish with the minimal pom that looks like
<project> <modelVersion>4.0.0</modelVersion> <groupId>com.coveo</groupId> <artifactId>fmt-maven-plugin</artifactId> <version>${VERSION_ALREADY_PUBLISHED}</version> <distributionManagement> <relocation> <groupId>com.spotify.fmt</groupId> </relocation> </distributionManagement> </project>
right? I might be wrong
I was thinking we would do this for one version, 2.14, and @malaporte could run deploy from this branch (once we change the version to 2.14 in it)
What I intended to do was to produce sort of the same small pom as above, but with the signing plugin as well. We could make pom in this PR even smaller.
Made the pom smaller
closing old PR
See also #129
What this would give is information similar to this one - https://mvnrepository.com/artifact/org.apache.commons/commons-io