chore: remove MaxPermSize JVM arg in gradle.properties

[aaron-congo]

Summary

chore: remove MaxPermSize JVM arg in gradle.properties

Description

The MaxPermSize JVM arg was recently added to gradle.properties (along with some other args) with the intent of allowing more memory so that the html test reporter would not receive an OutOfMemory error. However, in Java 8, MaxPermSize was replaced with MaxMetaspaceSize, so gradle would occasionally fail with Unrecognized VM option 'MaxPermSize=128m'. Additionally, by default, there is no limit on the MaxMetaspaceSize, so adding the arg actually adds stricter limits to the memory.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

1. Register at Qodana Cloud and configure the action
2. Use GitHub Code Scanning with Qodana
3. Host Qodana report at GitHub Pages
4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.3.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions