Repository navigation
docs: explain when to use the plugin in place of SDKMAN and compare their commands - #121
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs: explain when to use the plugin in place of SDKMAN and compare their commands.
docs/sdkman.mdanddocs/zh-CN/sdkman.mdare new. They say when the plugin is the right tool, give a table of 14 tasks with the SDKMAN command and the vfox command for each, and list what differs: the default distribution,vfox search javalisting OpenJDK only, installed names that carry a build number, a.sdkmanrcthat only selects, and so on.README.mdandREADME_CN.mdget a "Use cases" section. SDKMAN is a set of bash scripts and, by its own installation page, cannot be installed natively on Windows, so it cannot be used in PowerShell, not even in the Windows PowerShell 5.1 that comes with Windows. There the plugin takes its place.docs/sdkmanrc.mdand its Chinese page link to the new page.The SDKMAN side comes from sdkman.io's installation and usage pages and its public API, read on 2026-11-02. SDKMAN itself was not installed. The vfox commands were tried with vfox 1.0.13 and plugin 0.6.3 on Linux, except
vfox upgrade,vfox update javaandvfox use --global, which change the machine. The relative links and anchors in the docs resolve.The pages do not claim that vfox was tested in Windows PowerShell 5.1: the Windows e2e suite runs PowerShell 7 only. They say that SDKMAN cannot be used there and that vfox has a hook for PowerShell.