Sorry if any repeats. Juggling multiple accounts.
Our primary issue is snapshots not updating to sonatype despite all green from the CI
This seems to be the relevant message: "
Not uploading cache default-protected due to policy
"
Any ideas?
On 7/23/25 14:03, Jim Hargrave wrote:
for our snapshot build I see this:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:09 h
[INFO] Finished at: 2025-07-23T18:49:32Z
[INFO] ------------------------------------------------------------------------
Saving cache for successful job 00:01
Not uploading cache default-protected due to policy
Cleaning up project directory and file based variables 00:00Job succeeded
On 7/23/25 13:58, Jim Hargrave wrote:
yep two issues
- GitLab - upgrade open source license if needed
- Sonotype snapshots not updating
On 7/23/25 13:56, Mihai Nita wrote:
But that's GitLab, not Sonatype, right?
On Wed, Jul 23, 2025, 12:55 Mihai Nita <mih...@gmail.com> wrote:
I contacted them more than a week ago.After a few exchanges they went silent.I'll ping them againM
On Wed, Jul 23, 2025, 10:38 Jim Hargrave <jhargr...@gmail.com> wrote:
I also see this warning for gitlab:
Your Opensource subscription will expire on 2025-07-29
Your Opensource subscription for Okapi Framework will expire on 2025-07-29. If you do not renew by 2025-08-12, you can't use merge approvals, code quality, or any other paid features.
On 7/23/25 11:27, Jim Hargrave wrote:
We still have an openxml PR to support chartEx that needs to be finished and tested. The "code id" PR caused test failures so we had to revert that one. Needs to be resubmitted.
There is also a deployment issue where our SNAPSHOTS are not showing up on sonotype. The last deployed openxml artifacts are from June 30th. Not sure what is going on there - but probably related to the deployment changes made by sonotype. Denis tried to fix this and looked like it was working. At least we get no errors. But there must still be an issue.
Is there someone that can look at the sonotype issues?
Jim
On 7/23/25 00:00, yves.s...@gmail.com wrote:
--Hi Anders,
We do not have a fixed date yet. But we hope it’ll be soon.
@Jim: Any hint we can give Jim?
-ys
From: 'Anders Oesterholm' via okapi-users <okapi...@googlegroups.com>
Sent: Monday, July 21, 2025 11:42 AM
To: okapi-users <okapi...@googlegroups.com>
Subject: [okapi-users] 1.48.0 release date
Hi Okapi contributors,
I would like to ask if there is a planned release date for version 1.48.0 of the Okapi framework.
Best Regards
Anders
--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-users/16abf757-40c2-4782-be07-b5fe322bc670n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-users/000d01dbfb97%241e183ce0%245a48b6a0%24%40gmail.com.
This e-mail and any attachments are confidential and intended solely for the intended addressee. If you are not the intended addressee or have received this e-mail in error, please notify Straker immediately, delete it from your system and do not copy, disclose, distribute or otherwise act in reliance upon any part of this e-mail or its attachments. Straker will not be held liable for any damage caused by the message.
Is it necessary to print this email? If you care about the environment like we do, please refrain from printing emails. It helps to keep the environment forested and litter-free.
This e-mail and any attachments are confidential and intended solely for the intended addressee. If you are not the intended addressee or have received this e-mail in error, please notify Straker immediately, delete it from your system and do not copy, disclose, distribute or otherwise act in reliance upon any part of this e-mail or its attachments. Straker will not be held liable for any damage caused by the message.
Is it necessary to print this email? If you care about the environment like we do, please refrain from printing emails. It helps to keep the environment forested and litter-free.
This e-mail and any attachments are confidential and intended solely for the intended addressee. If you are not the intended addressee or have received this e-mail in error, please notify Straker immediately, delete it from your system and do not copy, disclose, distribute or otherwise act in reliance upon any part of this e-mail or its attachments. Straker will not be held liable for any damage caused by the message.
Is it necessary to print this email? If you care about the environment like we do, please refrain from printing emails. It helps to keep the environment forested and litter-free.
GitLab!!!!!!! You were supposed to be our friend :-)
Hi Jim, Mihai,
There is another merge request #931
with an attempt to get on with this issue. And I suggest Mihai's
comment as a deployment guide to Sonatype at the moment. It
is so valuable! Thank you, Mihai!
Hi Mihai, the GitLab Support team is going to resolve this bug for you.It's an internal issue with the billing system.Your license won't actually expire on 2025-07-29.It will continue through 2025-08-12 and we will have this all resolved for you before then to continue.Sorry again for the troubles here and appreciate your patience!