Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra step in documentation #11284

Closed
2 tasks done
InAnYan opened this issue May 8, 2024 · 0 comments · Fixed by #11295
Closed
2 tasks done

Extra step in documentation #11284

InAnYan opened this issue May 8, 2024 · 0 comments · Fixed by #11295

Comments

@InAnYan
Copy link
Collaborator

InAnYan commented May 8, 2024

JabRef version

5.13 (latest release)

Operating system

Windows

Details on version and operating system

No response

Checked with the latest development build (copy version output from About dialog)

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

This is a very little bug or even a typo, but nevertheless I decided to post it.

In devdocs on the page Step 2: Set up the build system: JDK and Gradle I think there is an extra step that we can just delete.

It is the image right after the:

Open the module settings: Right click on “JabRef” and select “Open Module Settings”:

This step is needed in order to setup the SDK for the project. But actually we were already on the needed window in the previous step "After clicking “Download”, IntelliJ installs Eclipse Temurin:". The window is the same "Project Structure", so there is no other need of an inderection "Open module settings".

Maybe I missed something and there is a specific reason for this step?

Appendix

...

Log File
Paste an excerpt of your log file here
@koppor koppor mentioned this issue May 14, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant