Add note regarding -ea being required for plugin tests

This commit is contained in:
Adam
2021-09-07 14:31:26 -04:00
parent f9a42db8fd
commit e35f88e7f5

View File

@@ -26,7 +26,7 @@ There are two methods to create an external plugin, you can either:
5. Open `build.gradle` and edit `runeLiteVersion` from `1.5.44-SNAPSHOT` to the latest release. If you are unsure about the current version it's specified on [runelite.net](https://runelite.net/).
6. In order to make sure everything works correctly, try to start the client with your external plugin enabled by running the test.
6. In order to make sure everything works correctly, try to start the client with your external plugin enabled by running the test. The test requires `-ea` to be added to your VM options to enable assertions, which can be found in IntellIJ in `Run/Debug Configurations` under `Modify options`, `Add VM options`, and then adding `-ea` into the input field which appears.
![run-test](https://i.imgur.com/tKSQH5e.png)
@@ -120,4 +120,4 @@ be have their cryptographic hash verified during the build to prevent [supply ch
To do this we rely on [Gradle's dependency verification](https://docs.gradle.org/nightly/userguide/dependency_verification.html).
To add a new dependency, add it to the `thirdParty` configuration in [`package/verification-template/build.gradle`](https://github.com/runelite/plugin-hub/blob/master/package/verification-template/build.gradle),
then run `../gradlew --write-verification-metadata sha256` to update the metadata file. A maintainer must then verify
the dependencies manually before your pull request will be merged.
the dependencies manually before your pull request will be merged.