You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The instructions in the README.md file need to be updated to ensure all developers are always installing the latest oscal-cli version. If maven path is consistent and only the version differs , maybe the version could be treated as a parameter in the installation description.
The text was updated successfully, but these errors were encountered:
For downloading the CLI from the official Maven OSSRH repositories, there is no alias for LATEST that will allow people to download directly (it would seem from casual interactions most people are using the CLI download it directly from the web-browser or with a HTTP client, like curl or wget, not with the Maven mvn utility where such an alias can be helpful). I can write a more complex shell expansion to alias the latest release, but will be system-specific and make the minimal documentation less approachable to people who do not understand the commands.
That said, I do see some value in improving the documentation. I will want triage this further, but I do not see it as a bug. I have some ideas how to clarify, but it will make the documentation slightly more complicated. Is a comment in the commands that says # Visit this URL and select the latest release sufficient? Somehow, an example URL will need to be in there then.
Describe the bug
The instructions in the README.md file need to be updated to ensure all developers are always installing the latest
oscal-cli
version. If maven path is consistent and only the version differs , maybe the version could be treated as a parameter in the installation description.The text was updated successfully, but these errors were encountered: