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
adpot-versions not working #206
Comments
Hi Ben.
It looks like @AdoptOpenJDK nuked all openjdk9/openjdk9-openj9 and openjdk10 releases.
The reason these don't work is because jabba is using semver ranges to match available versions. All AdoptOpenJDK builds are marked as "pre-release"s (they have |
Thanks a lot! In conjunction with #115 and more powerful aliases, this will work out just fine. e.g. oracle@latest, ibm@latest (which is now adopt-openj9), adopt@latest, adpot-openj9@latest etc. Would also be nice if shipped aliases had a description. Should I open another issue for this? |
|
Hi @shyiko, can you please elaborate "near completion"? :) |
I would like reopen this request since it's been more than a year and there's been no update (literally) |
Hi,
I have several problems installing adopt and adopt-openj9.
Also, aliases are not set property.
adpot alias
Given
When
jabba install adopt@1.9
Expected
(Installation)
Actual
compatible version found for adopt@1.9
adopt install
Given
jabba install adopt@1.9.0-181
Expected
(Install successfull)
Actual outcome
Same for adopt-openj9@*
alias of adopt-openj9
Given
When
jabba install adopt-openj9@1.9
Expected
(Install)
Actual outcome
The text was updated successfully, but these errors were encountered: