Changes between Version 3 and Version 4 of code/doc/Output

Timestamp:

Apr 12, 2017, 11:28:42 PM (8 years ago)

Author:

landauf

Comment:

fixed links

code/doc/Output

@@ -1 +1 @@
 = Output =
-[[TracNav(TracNav/TOC_Development)]]
 
 == Description ==
@@ -18 +17 @@
 Levels are used to define the meaning and the importance of an output message.
 
-See the [http://www.orxonox.net/doxygen/namespaceorxonox_1_1level.html doxygen page] or util/OutputDefinitions.h for a list of all output levels.
+See the [https://www.orxonox.net/jenkins/view/Management/job/orxonox_doxygen_trunk/javadoc/namespaceorxonox_1_1level.html doxygen page] or util/OutputDefinitions.h for a list of all output levels.
 
 Each level has a different meaning and a different priority. The {{{user_*}}} levels are used to provide the user with (sparse) information about the program's state. The {{{internal_*}}} levels are usually only visible in the log-file and are used by developers. The {{{verbose_*}}} levels are usually not visible (not even in the log-file) and are only activated in rare cases (debugging).
@@ -28 +27 @@
 Contexts give additional information about the part of the program that generated the output message. Contexts are basically just strings, which means they are identified by their name. It's possible to activate verbose output of only one context which allows debugging of specific parts of the program without being flooded with thousands of unrelated output messages.
 
-Most contexts are defined in [http://www.orxonox.net/doxygen/_output_definitions_8h.html util/OutputDefinitions.h], but there might exist more in different locations.
+Most contexts are defined in [https://www.orxonox.net/jenkins/view/Management/job/orxonox_doxygen_trunk/javadoc/_output_definitions_8h.html util/OutputDefinitions.h], but there might exist more in different locations.
 
 == Examples ==