Switch from Central Snapshots to JitPack

[koppor]

Central Snapshots is down now and then. Therefore, trying jitpack.

Also a follow-up to #13319 to have the build clean:

• remove jar files available on maven central
• Use official IC4J for JabKit (until we get our PR in)

Also follow-up to #13185 fixing JabSrvLauncher cc @palukku

Consequences:

• Good, because jitpack is more reliable these days than maven central regarding snapshots
• Bad, because jitpack does not instantly build, but has some delays and skips versions

Steps to test

 jbang --fresh .jbang/JabKitLauncher.java

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• [/] Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• [/] Screenshots added in PR description (if change is visible to the user)
• [/] 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.

[trag-bot]

Including GUI-related code in server components violates layered architecture principles. GUI code should only be a gateway, and complex operations should be in org.jabref.logic.

[koppor]

cc @subhramit :)

[koppor]

jitpack does not build the snapshot currently, but it works locally.

I merge and hope for the best :)

[trag-bot]

Commented code with explanation should be removed. Version control history should be used to track these changes instead of keeping commented code in the source.

[trag-bot]

GUI components are being sourced directly in the server package, violating the layered architecture principle. GUI code should be a gateway to logic code in org.jabref.logic.

[trag-bot]

Commented code should be removed as it serves no functional purpose. Git history should be used to track these changes instead of keeping commented code.

[Siedlerchr]

Jitpack is even more unreliable trag-bot[bot] ***@***.***> schrieb am Mi., 2. Juli 2025, 17:42:

…

***@***.***[bot]* commented on this pull request. ------------------------------ In .jbang/JabSrvLauncher.java <#13434 (comment)>: > +// disabled due to maven central issues +// DEPS org.jabref:jablib:6.+ Commented dependency declarations create confusion and clutter the code. Version history should be managed through git, not through commented code. — Reply to this email directly, view it on GitHub <#13434 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACOFZCXZVJQYM4XNWORV7D3GP4YDAVCNFSM6AAAAACAUKRWNOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDSNZZGY4DQNZTGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>