Include missing URL missed in translation from wiki.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196635 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/content/xdocs/dev/conventions.xml b/src/documentation/content/xdocs/dev/conventions.xml
index 320efbc474f3656204348635e779bdbf27f2b204..658a2e629db79eb5713dcd15c6f1977c34d59fec 100644 (file)
--- a/src/documentation/content/xdocs/dev/conventions.xml
+++ b/src/documentation/content/xdocs/dev/conventions.xml
@@ -82,7 +82,7 @@ This favors a clearer design and makes switching between implementations easier
           <li>Avoid using exceptions for flow control.</li>
           <li>Try to catch exceptions as much as possible and rethrow higher level exceptions (meaning hiding the low level detailed and putting a message that is more related to the function of your code).</li> 
           <li>It is important not to lose the stack trace which contains important information.
-Use chained exception for that. Avalon Framework provides [CascadingException] (and similar) for this.
+Use chained exception for that. Avalon Framework provides <jump href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</jump> (and similar) for this.
 Exception class names and stack traces must be treated like gold.
 Do whatever is required so that this information is not lost.
 Printing error messages to System.err or System.out is useless in a server-side environment where this info is usually lost.</li>