Update IntelliJ setup instructions with Gradle workaround#14234
Conversation
|
|
||
| ## Pre-condition: Gradle caches filled | ||
|
|
||
| On Linux, with IntelliJ IDEA 2025.2.4 (Ultimate Edition), there are issues with importing. |
There was a problem hiding this comment.
Are we sure the community edition doesn't have this issue?
There was a problem hiding this comment.
Haven't tried yet. Can try on Monday.
|
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.
Happens automatically by IntelliJ |
Co-authored-by: Subhramit Basu <subhramit.bb@live.in>
Pull request was converted to draft
|
Converted to draft - needs to be checked with IntelliJ Community Edition |
|
what's the status here`is this still necessary? |
IDK. It worked with the Community Edition on Debian 12. Step to test:
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. |
|
Side track - workflow https://github.com/JabRef/jabref/blob/main/.github/workflows/on-pr-labeled-update-pr-status.yml works Just adding label "ready for review" changes also the status of the PR. 
|
I had issues on a Linux machine. Here a tested workaround.
Steps to test
Setup development environment on Debian 12.
Mandatory checks
CHANGELOG.mdin a way that is understandable for the average user (if change is visible to the user)