Add workaround for IDEA-317606

[koppor]

When starting from scratch in IntelliJ, one might see java.lang.IllegalStateException: Module entity with name: jabref.main should be available. See IDEA-317606 for details.

This PR adds a work around (update): by changing settings.gradle.

The underlying issue is that in settings.gradle, we currently have JabRef as project name. However, our source repository is called jabref, which is not the same casing. This started to confuse IntelliJ.

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]

Still not working:

[koppor]

Closed IntelliJ, deleted .intellij folder and restarted IntelliJ (as recommended by https://youtrack.jetbrains.com/issue/IDEA-317606/Changing-only-the-case-of-the-Gradle-root-project-name-causes-exception-while-importing-project-java.lang.IllegalStateException#focus=Comments-27-7257761.0-0)

Works now

I would more like to use jabref as global configuration name - as we have the branding "JabRef" coded differently in our sources, don't we?

-rootProject.name = "JabRef"
+rootProject.name = "jabref"

[Siedlerchr]

not sure if this will affect our installer/deployment scripts etc

[koppor]

not sure if this will affect our installer/deployment scripts etc

Maybe we just try in this PR? -- I pushed the change in settings.gradle. Let's see how the binaries behave.

[koppor]

not sure if this will affect our installer/deployment scripts etc

The application name is NOT reused from there, but hard coded in the launcher part of jlink:

jabref/build.gradle

Line 554 in 9c4ca38

name = 'JabRef'

(Documentation at https://badass-jlink-plugin.beryx.org/releases/latest/ -> section "Launcher")

[koppor]

I checked the build portable version locally - works fine:

This is good. If the branding of our applicatian relied on some gradle configuration, I would find that strange. (Changing the name to CloudRef via a single line?)

[github-actions]

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

[koppor]

Note that the proejct name change was reverted in 08a7f8d as hotfix. I don't remember the reasons excactly, but the macOS build was not working any more.

I tried to redo at #10345, but macOS still did not work.