Skip to content

Conversation

@koppor
Copy link
Member

@koppor koppor commented Jul 9, 2024

Fixes #11465

Reason: In #11195, we introduced applicationDefaultJvmArgs, which are required to be passed to java launcher.

The existing script (introduced in 2020, #6439), did pass a wrong parameter -p. It was not noticed, because the path was not found (one ../ was missing). Now, we need this config "somehow", because of this #11195.

Mandatory checks

  • Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
  • Tests created for changes (if applicable)
  • Manually tested changed features in running JabRef (always required)
  • Screenshots added in PR description (for UI changes)
  • Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

koppor and others added 2 commits July 9, 2024 22:04
@koppor koppor added the platform: snap When JabRef is run as a snap on linux label Jul 9, 2024
@koppor koppor enabled auto-merge July 9, 2024 20:10
@koppor koppor disabled auto-merge July 9, 2024 20:33
@koppor koppor merged commit 6b8e95d into main Jul 9, 2024
@koppor koppor deleted the fix-snapcraft branch July 9, 2024 20:33
@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2024

The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

platform: snap When JabRef is run as a snap on linux

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jabref snap fails to start on ubuntu

4 participants