-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: what is the recommended process for renaming a package #699
Comments
Hi @ezzarghili 👋 I'm a bit confused about this. We currently host two variants of GraalVM, namely the Oracle packages (identified by
Not sure what that means. Is that on the SDKMAN website or somewhere else? We have nothing called GCN right now.
The entire project is driven by dynamic data. If you are referring to the individual versions that we host, they are all in a database. Renaming these historic versions would require a data migration on our side. Also, we point to the actual binaries on the Internet, so I hope that you are not proposing renaming the actual web resources, as that would cause widespread breakage. |
Hi @ezzarghili, no apologies from me for not fully understanding the context! We don't currently have a process for renaming a candidate, so I might need to do this manually against our database using some scripts. Also, are you currently publishing your releases using our vendor API? If so, that would also need some changes. Lastly, can you send me how the new copy should read on our website? Once I have all these bits, I can look into doing it all in one go. |
Hello,
The GCN (Graal Cloud Native) project and its tools are being renamed to GDK (Graal Dev Kit).
This has been already reflected on the website and repo, artifacts update is scheduld for next release on July 16th 2024 .
I was wondering what would be the best way to approch this in SDKMAN?
Thanks
The text was updated successfully, but these errors were encountered: