JabRef
Add template engine ADR
Mandatory checks
~- [ ] Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)~
~- [ ] Tests created for changes (if applicable)~
~- [ ] Manually tested changed features in running JabRef (always required)~
~- [ ] Screenshots added in PR description (for UI changes)~
~- [ ] 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.~
Refs https://github.com/koppor/jabref/issues/392
I think you understand this is unfinished ADR, because I haven't used layout files and template engines much in Java.
I wrote everything for AI, and every option seems to be fine
- [x] Please add the arguments of https://stackoverflow.com/a/1984458/873282 as pros/and cons. You can reference the answer as soruce:
[[source](https://stackoverflow.com/a/1984458/873282)]
Reading the syntax, +1 for Velocity.
Velocity's goal is to keep templates as simple as possible
From: https://stackoverflow.com/a/1984458/873282
And this is what we mainly want!
I chose Apache Velocity
Sorry, on your all behalf :)
I want to complete this ADR