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
Copy file name to clipboardExpand all lines: README.md
+3-26Lines changed: 3 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,32 +23,9 @@ All SDKMAN's BDD tests describing the CLI behaviour are written in Cucumber and
23
23
24
24
$ ./gradlew test
25
25
26
-
To perform development, you will need to have a JDK 8 or higher installed which can be obtained by running the following after installing SDKMAN:
26
+
To perform development, you will need to have a JDK 11 installed which can be obtained by running the following after installing SDKMAN:
27
27
28
-
$ sdk install java
29
-
30
-
### Using Docker for tests
31
-
32
-
You can run the tests in a Docker container to guarantee a clean test environment.
33
-
34
-
$ docker build --tag=sdkman-cli/gradle .
35
-
$ docker run --rm -it sdkman-cli/gradle test
36
-
37
-
By running the following command, you don't need to wait for downloading Gradle wrapper and other dependencies. The test reports can be found under the local `build` directory.
38
-
39
-
$ docker run --rm -it -v $PWD:/usr/src/app -v $HOME/.gradle:/root/.gradle sdkman-cli/gradle test
40
-
41
-
### Local Installation
42
-
43
-
To install SDKMAN locally running against your local server, run the following commands:
44
-
45
-
$ ./gradlew install
46
-
$ source ~/.sdkman/bin/sdkman-init.sh
47
-
48
-
Or run install locally with Production configuration:
49
-
50
-
$ ./gradlew -Penv=production install
51
-
$ source ~/.sdkman/bin/sdkman-init.sh
28
+
$ sdk env install
52
29
53
30
## Contributors
54
31
@@ -76,4 +53,4 @@ Support this project by becoming a sponsor. Your logo will show up here with a l
0 commit comments