Index: doc/building.md =================================================================== diff -u -N -rad9c32bd7fc4908dfef14834564aaa5557601a26 -rf3dcb2f8f602117ac390799b1f310dcaa9918592 --- doc/building.md (.../building.md) (revision ad9c32bd7fc4908dfef14834564aaa5557601a26) +++ doc/building.md (.../building.md) (revision f3dcb2f8f602117ac390799b1f310dcaa9918592) @@ -9,7 +9,7 @@ cd jalview gradle shadowJar # run -java -jar build/libs/jalview-all-11.jar +java -jar build/libs/jalview-all-*-j11.jar # and/or create launcher gradle getdown @@ -248,20 +248,23 @@ file. A default launching class (`MAIN-CLASS: jalview.bin.Launcher`) is specified in the `.jar` manifest file (`META/MANIFEST.MF`) so a start class doesn't need to be specified. -Build the shadow jar file in `build/lib/jalview-all-11.jar` with +Build the shadow jar file in `build/libs/jalview-all-VERSION-j11.jar` with ```bash gradle shadowJar ``` -and run it with +__NB__ `VERSION` will be replaced with a version number or "`DEVELOPMENT`" depending on how the branch is set up. + +Run it with + ```bash -java -jar build/lib/jalview-all-11.jar +java -jar build/libs/jalview-all-VERSION-j11.jar ``` Because no arguments are required, most OSes will associate a `.jar` file with the `java` application (if this has been installed through the OS and not just a local -unzip) as a `-jar` argument so you may find you can launch `jalview-all-11.jar` +unzip) as a `-jar` argument so you may find you can launch `jalview-all-VERSION-j11.jar` just by double-clicking on it)! > The `shadowJar` task is not a requirement for any other task, so to build the shadow