Update IntelliJ setup instructions with Gradle workaround

[koppor]

I had issues on a Linux machine. Here a tested workaround.

Steps to test

Setup development environment on Debian 12.

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user 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 updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

[subhramit]

Are we sure the community edition doesn't have this issue?

[koppor]

Haven't tried yet. Can try on Monday.

[Siedlerchr]

Have you tried to increse java memory heap size in intellij?
Did you import as gradle project after cloning?

[koppor]

Have you tried to increse java memory heap size in intellij?

No. 16 GB RAM of the machine was already full.

IntelliJ ran OKish, but gradle was unable to compile its Kotlin build files.

Did you import as gradle project after cloning?

Happens automatically by IntelliJ

[koppor]

Converted to draft - needs to be checked with IntelliJ Community Edition

[Siedlerchr]

what's the status here`is this still necessary?

[koppor]

what's the status here`is this still necessary?

IDK.

It worked with the Community Edition on Debian 12.

Step to test:

1. Clean VM (maybe https://github.com/JabRef/jabref/tree/main/scripts/vms/debian-12)
2. Test intellij ultimate
3. Clean VM (maybe https://github.com/JabRef/jabref/tree/main/scripts/vms/debian-12)
4. Test intellij community

By "Test" I mean: First the normal instructions - and then this patched ones - and see if the normal ones do not work and the patched ones do. Maybe, we need to add "If you use ultimate" - or we need to add some hints that if gradle import goes wrong.