📦 jmc/ openjdk

Running Tests

To run the unit tests:

mvn verify

To run the UI tests:

mvn verify -P uitests

Note that the UI tests will take some time to run, and that you need to stop interacting with your computer for the duration of the tests.

Spotbugs can take some time to run. If you are only interested in the test results, you can skip running spotbugs by setting -Dspotbugs.skip=true.

For example:

mvn verify -P uitests -Dspotbugs.skip=true

Running the Locally Built JMC

The built JMC will end up in the target folder in the root. The launcher is located in target/products/org.openjdk.jmc/<platform>. By default whichever JRE is on the path will be used. Remember to set it to a JDK (rather than a JRE) if you want the launched mission control to automatically discover locally running JVMs. To override which JVM to use when launching, add -vm and the path to a directory where a JDK java launcher is located, for example -vm $JAVA_HOME/bin.

Here is an example for Mac OS X:

# on aarch64 (M1/M2/M3/M4)
target/products/org.openjdk.jmc/macosx/cocoa/aarch64/JDK\ Mission\ Control.app/Contents/MacOS/jmc

# on x86_64 (Intel)
target/products/org.openjdk.jmc/macosx/cocoa/x86_64/JDK\ Mission\ Control.app/Contents/MacOS/jmc

Here is an example for Linux:

# on x86_64
target/products/org.openjdk.jmc/linux/gtk/x86_64/JDK\ Mission\ Control/jmc

# on aarch64
target/products/org.openjdk.jmc/linux/gtk/aarch64/JDK\ Mission\ Control/jmc

And here is an example for Windows x64:

"target\products\org.openjdk.jmc\win32\win32\x86_64\JDK Mission Control\jmc"