diff --git a/docs/decisions/0039-use-apache-velocity-as-template-engine.md b/docs/decisions/0039-use-apache-velocity-as-template-engine.md
index 5e6ca8d1072..fd5d53ea7ef 100644
--- a/docs/decisions/0039-use-apache-velocity-as-template-engine.md
+++ b/docs/decisions/0039-use-apache-velocity-as-template-engine.md
@@ -54,6 +54,7 @@ ${CanonicalBibEntry.getCanonicalRepresentation($entry)}
 * Good, because it has simple syntax, and it is designed for simple template workflows.
 * Good, because it has a stable syntax ([source](https://stackoverflow.com/a/1984458/10037342)).
 * Bad, because it is in maintenance mode.
+* Bad, because [removed from Spring 5.0.1](https://www.baeldung.com/spring-template-engines#other-template-engines)
 
 ### Apache FreeMarker
 
@@ -107,4 +108,7 @@ Here are the papers you are analyzing:
 
 As stated in [the template discussion issue](https://github.com/koppor/jabref/issues/392), we should choose a template engine, and then slowly migrate previous code and templates to the chosen engine.
 
+Other template engines are discussed at <https://www.baeldung.com/spring-template-engines>, especially [`#other-template-engines`](https://www.baeldung.com/spring-template-engines#other-template-engines).
+We did not find any other engine there being worth switchting.
+
 <!-- markdownlint-disable-file MD004 -->