JabRef Developer Documentation
Overview on Developing
Table of contents
Architectural Decisions
Contributing
JabRef and Software Engineering Training
Adr
Use Markdown Architectural Decision Records
Use Crowdin for translations
Use slf4j together with log4j2 for logging
Use Gradle as build tool
Use MariaDB Connector
Fully Support UTF-8 Only For LaTeX Files
Only translated strings in language file
Provide a human-readable changelog
Use `public final` instead of getters to offer access to immutable variables
Use Plain JUnit5 for advanced test assertions
Use H2 as Internal SQL Database
Test external links in documentation
Handle different bibentry formats of fetchers by adding a layer
Add Native Support for BibLatex-Software
Separate URL creation to enable proper logging
Query syntax design
Mutable preferences objects
Allow org.jabref.model to access org.jabref.logic
Use regular expression to split multiple-sentence titles
MADR Template
Advanced reading
Advanced reading
Code Quality
Custom SVG icons
Working on fetchers
Creating a binary and debug it
Remote Storage
Recommendations for UI design
Getting into the code
Getting into the code
Code Howtos
JabRef's development strategy
Set up a local workspace
High-level documentation
How to test
Readings on coding
Readings on Coding
Readings on JavaFX
Useful development tooling
JabRef Developer Documentation
Docs
»
Getting into the code »
Getting into the code
Edit on GitHub
Getting into the code
GitHub
« Previous
Next »