ack java -jar in Metabase

java-jar.txt

$ ack 'java -jar'
src/metabase/db/setup.clj
137:                       (trs "You must run `java -jar metabase.jar migrate down` from version {0}." latest-applied)

src/metabase/db/liquibase.clj
236:           (trs "You can force-release these locks by running `java -jar metabase.jar migrate release-locks`."))))))

src/metabase/core.clj
222:    (run-cmd cmd init! args) ; run a command like `java -jar metabase.jar migrate release-locks` or `clojure -M:run migrate release-locks`

src/metabase/models/cloud_migration.clj
311:  ;;   java -jar metabase.jar dump-to-h2 dump --dump-plaintext

src/metabase/cmd/dump_to_h2.clj
10:    java -jar metabase.jar dump-to-h2

src/metabase/cmd/load_from_h2.clj
8:    java -jar metabase.jar load-from-h2

src/metabase/cmd/resources/env-var-intro.md
31:java -jar metabase.jar

src/metabase/cmd.clj
10:    java -jar metabase.jar migrate force

release/README.md
24:4. Test the built jar locally: `MB_JETTY_PORT=3033 java -jar target/uberjar/metabase.jar`

docs/databases/encrypting-details-at-rest.md
29:   MB_ENCRYPTION_SECRET_KEY="IYqrSi5QDthvFWe4/WdAxhnra5DZC3RKx3ZSrOJDKsM=" java -jar metabase.jar
51:MB_ENCRYPTION_SECRET_KEY=your-current-key java -jar metabase.jar rotate-encryption-key new-key
61:MB_ENCRYPTION_SECRET_KEY="your-current-key" java -jar metabase.jar rotate-encryption-key ""

docs/troubleshooting-guide/loading-from-h2.md
47:    java -jar metabase.jar load-from-h2 /path/to/metabase.db # do not include .mv.db
76:    java -jar metabase.jar migrate release-locks

docs/installation-and-operation/running-the-metabase-jar-file.md
25:java -jar metabase.jar
86:java -jar metabase.jar
129:You'll create a directory for your Metabase like in the steps listed above for the [Local installation](#local-installation), but when it's time to run the `java -jar` command to start up the JAR, you'll prefix the command with some environment variables to tell Metabase how to connect to the `metabaseappdb` you created:
138:java -jar metabase.jar

docs/installation-and-operation/running-metabase-on-debian.md
59:ExecStart=/usr/bin/java -jar </your/path/to/metabase/directory/>metabase.jar

docs/installation-and-operation/configuring-application-database.md
32:java -jar metabase.jar
45:java -jar metabase.jar
54:java -jar metabase.jar
72:java -jar metabase.jar
85:java -jar metabase.jar
95:java -jar metabase.jar
124:java -jar metabase.jar

docs/installation-and-operation/serialization.md
383:java -jar metabase.jar export dir_name
393:java -jar metabase.jar help export
419:java -jar metabase.jar export export_name --collection 1,2,3
447:java -jar metabase.jar import path_to_export
457:java -jar metabase.jar help import

docs/installation-and-operation/backing-up-metabase-application-data.md
26:4. Restart Metabase: `java -jar metabase.jar` or start the service again.

docs/installation-and-operation/upgrading-metabase.md
39:   java -jar metabase.jar
156:java -jar metabase.jar migrate down

docs/installation-and-operation/monitoring-metabase.md
22:Monitoring a remote Metabase instance (or a local instance running in a docker container) is probably more common, but requires a more setup. First we need to specify some system properties that lets the JVM know that we want to allow remote monitoring. Assuming we are running Metabase using `java -jar metabase.jar`, we'd need change the invocation to the below command, which includes the properties:

docs/installation-and-operation/migrating-from-h2.md
73:java -jar metabase.jar load-from-h2 /path/to/metabase.db # do not include .mv.db
93:java -jar metabase.jar
141:java -jar metabase.jar load-from-h2 /path/to/metabase.db # do not include .mv.db

docs/installation-and-operation/observability-with-prometheus.md
18:MB_PROMETHEUS_SERVER_PORT=9191 java -jar metabase.jar

docs/installation-and-operation/commands.md
10:java -jar metabase.jar help

docs/configuring-metabase/log-configuration.md
68:java -jar metabase.jar

docs/configuring-metabase/customizing-jetty-webserver.md
16:    java -jar metabase.jar
25:    java -jar metabase.jar
35:    java -jar metabase.jar

docs/configuring-metabase/config-file.md
227:MB_PREMIUM_EMBEDDING_TOKEN="[your token]" java -jar metabase.jar

docs/configuring-metabase/environment-variables.md
31:java -jar metabase.jar

docs/people-and-groups/changing-session-expiration.md
19:MAX_SESSION_AGE=1440 java -jar metabase.jar
47:MB_SESSION_COOKIES=true java -jar metabase.jar

docs/people-and-groups/managing.md
98:    java -jar metabase.jar reset-password [email protected]

enterprise/frontend/src/embedding-sdk/README.md
96:java -jar metabase.jar

.github/actions/build-ee-extra/action.yml
109:      run: java -jar ./bin/docker/metabase.jar &

.github/workflows/pre-release.yml
110:        run: java -jar ./metabase.jar &

.github/workflows/uberjar.yml
73:      run: java -jar ./target/uberjar/metabase.jar &

test/metabase/db/setup_test.clj
129:             Exception #"You must run `java -jar metabase.jar migrate down` from version 45."
136:             Exception #"You must run `java -jar metabase.jar migrate down` from version 46."

bin/build-for-test
16:  # java -jar target/uberjar/metabase.jar version | grep -oE 'source_hash [a-f0-9]+' | awk '{ print $2 }'