You could upload a relocation pom[1] or create a list of old and new groupId/ArtifactId combinations and use the oga-maven-plugin[2] to convert each project. Unfortunately that plugin only can fail your build and not output a warning.
[1] https://maven.apache.org/guides/mini/guide-relocation.html [2] https://github.com/jonathanlermitage/oga-maven-plugin Hth, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Fri, Mar 26, 2021 at 9:38 PM Martin Bradley <martsbrad...@googlemail.com.invalid> wrote: > Hi Folks, > > A large company moved to Maven and uploaded many of their non public jars > into the private company repository. Many of these dependencies were > uploaded without using standard group/artifact id. This is not easily > fixed > because many projects reference those group/artifact coordinates, changing > the > names needs much management and coordination across teams. > > The problem currently is the group/artifact ids are not following the > correct > convention of reverse dns name like com.someenterprise.dept. Therefore it > is > not easy to identify all the private jars under some particular folder > under ~/.m2/repo since they are scattered everywhere. > > Looking for how to build new versions of these jars and upload with a > corrected > group/artifact. While continuing to upload with the with the original > group/artifact id. A deadline for projects to switch to the corrected > group/artifact can be set. After the deadline we would just update the pom > to > use the corrected group/artifact and remove mentions of the old > coordinates. > > I had a look over various plugins but could not see a good way to handle > this. > > thanks. > Martin >
