Support for new shard of oss.sonatype - s01.oss.sonatype.org

[ghostbuster91]

Hi,

According to https://central.sonatype.org/articles/2021/Feb/23/new-users-on-s01osssonatypeorg/ new users are given access to s01.oss.sonatype.org and have to perform publishing through this server. This issue emerged also on sbt-sonatype repository: xerial/sbt-sonatype#214

I think the solution presented by @steinybot in xerial/sbt-sonatype#215 is quite good.

I will be happy to contribute that change, but before jumping into the code I would like to hear your opinion.

Cheers,
Kasper

[lefou]

The mill.scalalib.publish.SonatypePublisher already supports parametrized repository urls. The default urls are defined in mill.scalalib.PushlishModule.sonatypeUri and mill.scalalib.PushlishModule.sonatypeSnapshotUri, and can be overridden in your module.

[ghostbuster91]

Hi, thanks for the tip. It indeed worked. For any future readers here is what I did:

trait MyPublishModule extends PublishModule {
  def sonatypeUri: String = "https://s01.oss.sonatype.org/service/local"

  def sonatypeSnapshotUri: String =
    "https://s01.oss.sonatype.org/content/repositories/snapshots"
}

Unfortunately, this configuration isn't being picked up when using publishAll syntax and has to be duplicated:

./mill -i mill.scalalib.PublishModule/publishAll --publishArtifacts __.publishArtifacts --sonatypeUri "https://s01.oss.sonatype.org/service/local" 

Is there any way to workaround that?