<@U05DGS1P686> A bit YOLO but might work <https://...
# wiremock-java
o
πŸ‘ 1
After a few patches I am still stuck with Error 401 from Nexus. Unless something is completely wrong, the credentials should work, because I use the same in the Testcontainers Java module release flow
There might be escaping issues though
d
the "old" distribution mechanism is still in the gradle files
can there be any conflict
?
and it definitely is 0ss.sonatybe? not s01.oss.sonatype?
o
This is what we were said in https://issues.sonatype.org/browse/OSSRH-95888 . The entire
org.wiremock
group is on the legacy server
d
k - just checking
o
can there be any conflict
Might be. Trying the password first
I also broke the CI, sorry πŸ€¦β€β™‚οΈ
I will disable signing for CI, something got broken
d
np - in german: wo gehobelt wird, fallen SpΓ€ne. In english more or less: if you work, there are side effects
πŸ˜ƒ 1
o
Every Maven Central encounter ends up with a bunch of burned releases for me 😞
d
I initially started with a release on s01 - but never pushed anything:
Screenshot 2023-10-30 at 11.18.07.png
so I don't think this can cause a side effect
o
By the way, maybe we chould change the artifactId before releasing. Most of the projects actually use the
wiremock-${purpose}-extension
pattern, and I think it would be useful to rename before we declare Maven Central done, wdyt?
d
sure - got ahead
should we change the repo name as well then?
o
Would be nice. I can do the bulk change
πŸ‘ 1
FYI https://github.com/wiremock/wiremock-state-extension/pull/89 . Will retry the release after merging
d
thx
o
So the release still fails, and I am out of ideas. I guess I will submit a ticket to OSSRH. The same creds work in another release flow, for Maven though
d
😞