Migrations.md

@@ -8,6 +8,7 @@ When an application is already deployed and changes to the database are necessar
 4. Check the `build.gradle.kts` file and find the `h2Version` variable. In the `classpath` variable, replace `VERSION` with the version as it appears in the variable.
 5. Check the following path in your file explorer: `$HOME\.gradle\caches\modules-2\files-2.1\com.h2database\h2\VERSION` and find the folder containing a `.jar` file. Replace `HASH` in the `classpath` variable with the name of this folder.
    * If you can't find `modules-2` in the `.gradle/caches` folder, then check the [Gradle Docs](https://docs.gradle.org/current/userguide/directory_layout.html) and replace `modules-2` with the folder labeled `Shared caches (e.g. for artifacts of dependencies)`.
+   * Alternatively, you can opt to install the `.jar` file using the relevant version of H2 available on [Maven Central](https://mvnrepository.com/artifact/com.h2database/h2). When executing the migration process (see below), include an extra `--classpath` flag, specifying the file path to the installed `.jar` file.
 6. On a new line add the variable `changeSetAuthor` and set it equal to your GitLab username (usually your NetID).
 
 Another option is to obtain `h2.jar` and `liquibase.zip` from another developer (or from the `.gradle` folder). Then add Liquibase to your path and put the jar under `/usr/local/apps/h2`.