Mention of Java eco system WTFs

[koppor]

I wonder why your text in the beginning is a bit superficial.

I think, it is good to mention

• Split package problem when using java modules -- maybe something like "langchain4j was not easily usable in the JabRef context due to JabRef making use of JDK's modularization features"
• Add usage of java Command-Line Argument File on Windows -- maybe something like: "At the beginning, it was not possible to debug JabRef on Windows, because the command line generated by gradle grew too large". And maybe: "Debugging using IntelliJ's compiler was not possible, because langchain4j was not modularized correctly"

I think, both of them were unexpected at the beginning of the project. And it causes headaches at your and my side. I would have rather spend time in discussing JabRef architecture things, like replacing the Background Task handling by libraries such as Mutiny. With having time lost at these WTF Java eco system issues, we could not work on JabRef itself.

[koppor]

We are "forced" to use a text area because of copy feature, because of nearly 10 years old BUG in JavaFX https://bugs.openjdk.org/browse/JDK-8091644.

Source: InAnYan/jabref#169

[InAnYan]

Updated the project. Can you check?

Sorry, forgot to add link to this issue in the commit message

[koppor]

Either add some text (be precise) or leave it out.

I already made text proposals above.

[InAnYan]

@koppor here is the text https://github.com/InAnYan/gsoc?tab=readme-ov-file#challenges-and-important-things-you-learned-during-the-project

I used your text proposals mainly..

[koppor]

Small follow-up: #10