This will support specifying EA versions in the following format examples. E.g.:
14-ea
14.0.0-ea
14.0.0-ea.28
Notes:
- For the last form above, which is needed for requesting a specific ea build, we must only add '.x' if there are less than 3 dots in the version, hence the change from != 3 to < 3
- The prior parsing logic for e.g. 14.0.0-ea "spelling" will ignore precedence between build numbers in the form of e.g. 14.0.0-ea+b27 vs. 14.0.0-ea+b27 (so it will end up with the earliest rather than the latest ea build in the cdn), and does not allow specifying an ea build number (it will match 14.0.0-ea+b29 to a cdn 14.0.0-ea+b2). The new logic [copupled with the CDN populating EA builds in the form 14.0.0-ea.28) will resolve that.
author Bryan Clark <clarkbw@github.com> 1573862473 -0800
committer Bryan Clark <clarkbw@github.com> 1574976093 -0800
Adding maven auth support
ignore vscode directory
move required parameters to auth module
username and password are required from within the auth module now. Update the tests to ensure this is the case.
Add generated auth and setup-java
Move auth to the bottom of setup
Support ids
generated and pretty files
use server-id instead of ambigous id
Use console.log where appropriate
Adding maven auth support
ignore vscode directory
move required parameters to auth module
username and password are required from within the auth module now. Update the tests to ensure this is the case.
Add generated auth and setup-java
Move auth to the bottom of setup
generated and pretty files
use server-id instead of ambigous id
