A bit YOLO but might work

Question

< Dirk Bolte> A bit YOLO but might work

Oleg Nenashev · Answer

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

Oleg Nenashev · Answer

There might be escaping issues though

Dirk Bolte · Answer

the old distribution mechanism is still in the gradle files

Dirk Bolte · Answer

can there be any conflict

Dirk Bolte · Answer

and it definitely is 0ss sonatybe not s01 oss sonatype

Oleg Nenashev · Answer

This is what we were said in <https issues sonatype org browse OSSRH 95888> The entire `org wiremock` group is on the legacy server

Dirk Bolte · Answer

k just checking

Oleg Nenashev · Answer

gt can there be any conflict Might be Trying the password first

Oleg Nenashev · Answer

I also broke the CI sorry man facepalming

Oleg Nenashev · Answer

I will disable signing for CI something got broken

Dirk Bolte · Answer

np in german wo gehobelt wird fallen Späne In english more or less if you work there are side effects

Oleg Nenashev · Answer

Every Maven Central encounter ends up with a bunch of burned releases for me disappointed

Dirk Bolte · Answer

I initially started with a release on s01 but never pushed anything

Dirk Bolte · Answer

Screenshot 2023 10 30 at 11 18 07 png

Dirk Bolte · Answer

so I don t think this can cause a side effect

Oleg Nenashev · Answer

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

Dirk Bolte · Answer

sure got ahead

Dirk Bolte · Answer

should we change the repo name as well then

Oleg Nenashev · Answer

Would be nice I can do the bulk change

Oleg Nenashev · Answer

FYI <https github com wiremock wiremock state extension pull 89> Will retry the release after merging

Dirk Bolte · Answer

thx

Oleg Nenashev · Answer

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

Dirk Bolte · Answer

disappointed