Skip to content

Commit 6c244ae

Browse files
committedOct 31, 2024
8285: Documentation fix
Reviewed-by: aptmac
1 parent 5c49e6b commit 6c244ae

File tree

1 file changed

+21
-4
lines changed

1 file changed

+21
-4
lines changed
 

‎README.md

+21-4
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,9 @@ Prerequisites for building Mission Control:
215215

216216
1. Install a JDK 17 distribution and make sure it is declared in the local maven toolchain `~/.m2/toolchains.xml`
217217

218-
2. Install Maven (version 3.5.x. or above)
218+
2. Install a JDK 21 distribution and make sure that it too is declared in the local maven toolchain.
219+
220+
3. Install Maven (version 3.5.x. or above)
219221

220222
On Linux or macOS you can use the `build.sh` script to build JMC:
221223
```
@@ -227,15 +229,30 @@ usage: call ./build.sh with the following options:
227229
--clean to run maven clean
228230
```
229231

230-
Otherwise follow the steps manually:
232+
Otherwise follow the steps manually.
233+
234+
## Building JMC Step-by-Step
235+
236+
Here are the individual steps:
237+
238+
1. Get the third-party dependencies into a local _p2_ repo and make it available on localhost.
239+
240+
2. Build and install the core libraries.
231241

232-
First get third party dependencies into a local _p2_ repo and make it available on localhost:
242+
3. Build the JMC application.
243+
244+
First, if on Mac / Linux:
233245

234246
```bash
235-
cd missioncontrol-folder # where you just cloned the sources
236247
mvn p2:site --file releng/third-party/pom.xml; mvn jetty:run --file releng/third-party/pom.xml
237248
```
238249

250+
Or, if on Windows:
251+
252+
```bash
253+
mvn p2:site --file releng\third-party\pom.xml && mvn jetty:run --file releng\third-party\pom.xml
254+
```
255+
239256
Then in another terminal (in the project root):
240257

241258
```bash

0 commit comments

Comments
 (0)
Please sign in to comment.