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
and all of the supporting libraries in <code>j11lib/*.jar</code> merged into one <code>.jar</code> archive
file. A default launching class (<code>MAIN-CLASS: jalview.bin.Launcher</code>) is specified in the <code>.jar</code>
manifest file (<code>META/MANIFEST.MF</code>) so a start class doesn't need to be specified.</p>
-<p>Build the shadow jar file in <code>build/lib/jalview-all-11.jar</code> with</p>
+<p>Build the shadow jar file in <code>build/libs/jalview-all-VERSION-j11.jar</code> with</p>
<pre><code class="language-bash">gradle shadowJar
</code></pre>
-<p>and run it with</p>
-<pre><code class="language-bash">java -jar build/lib/jalview-all-11.jar
+<p><strong>NB</strong> <code>VERSION</code> will be replaced with a version number or "<code>DEVELOPMENT</code>" depending on how the branch is set up.</p>
+<p>Run it with</p>
+<pre><code class="language-bash">java -jar build/libs/jalview-all-VERSION-j11.jar
</code></pre>
<p>Because no arguments are required, most OSes will associate a <code>.jar</code> file with the
<code>java</code> application (if this has been installed through the OS and not just a local
-unzip) as a <code>-jar</code> argument so you may find you can launch <code>jalview-all-11.jar</code>
+unzip) as a <code>-jar</code> argument so you may find you can launch <code>jalview-all-VERSION-j11.jar</code>
just by double-clicking on it)!</p>
<blockquote>
<p>The <code>shadowJar</code> task is not a requirement for any other task, so to build the shadow
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
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