Taro L. Saito
Taro L. Saito
I didn't know Sonatype's preference about the organization names. I think most of sbt-sonatype users don't know neither. OK. Introducing this change as a major version makes sense (sbt-sonatype 4.0)....
As sbt-sonatype is used in more than 3000+ projects https://github.com/search?l=Scala&q=%22org.xerial.sbt%22+%25+%22sbt-sonatype%22&type=Code, introducing this breaking change would not worth the time of OSS developers. Let me close this PR because I don't...
I think we need to confirm two things: - A: Is sbt-sonatype accessing the endpoints in https://s01.oss.sonatype.org? This configuration is extracted here from the project https://github.com/xerial/sbt-sonatype/blob/245cf62923595ae9605d80bc3c5bf8942538799c/src/main/scala/xerial/sbt/Sonatype.scala#L416 - B: Is there...
@pomadchin Thanks. It seems @darkfrog26 also has this setting, but experiencing the same error occasionally: ``` ThisBuild / sonatypeCredentialHost := "s01.oss.sonatype.org" ``` To identify the cause, adding some info log...
It looks like the issue of configuration scopes. I guess depending on the context within sbt, extracting project settings via Project.extract(state) references unexpected projects. https://github.com/xerial/sbt-sonatype/blob/245cf62923595ae9605d80bc3c5bf8942538799c/src/main/scala/xerial/sbt/Sonatype.scala#L412 An approach would be changing...
Probably I've found the cause: https://github.com/xerial/sbt-sonatype/blob/245cf62923595ae9605d80bc3c5bf8942538799c/src/main/scala/xerial/sbt/Sonatype.scala#L68 This setting is not referencing `ThisBuild / sonatypeCredentialHost`, so the setting might vary depending on the context project. If that's the case, your log...
Released sbt-sonatype 3.9.12 with a fix in #285. I'm not sure this will solve the problem, but let me know if you still experience the issue.
We need to release a new version, which fixes this regression. Use sbt-sonatype 3.9.11 for a while. I'm a bit busy this week
Released sbt-sonatype 3.9.13, which reverted #276.
As I commented in #49, if there is a proper way to define a task that is enabled only at the root project, I'm happy to do so.