FYI The reason we needed to do this was due to the way the maven-publish plugin works when combined with the auto repository creation on oss.sonatype.org
The fix in this PR prevents it -- it's only needed for any repos with multiple sub projects, and was of course most obvious when initially porting egeria itself to v4/gradle.
FYI The reason we needed to do this was due to the way the maven-publish plugin works when combined with the auto repository creation on oss.sonatype.org
Here's another example post https://stackoverflow.com/questions/72664149/gradle-maven-publish-sonatype-creates-multiple-repositories-that-cant-be-clos
The fix in this PR prevents it -- it's only needed for any repos with multiple sub projects, and was of course most obvious when initially porting egeria itself to v4/gradle.