Merge pull request #557 from kieker-monitoring/KIEKER-1982

Kieker 1982

documentation/kieker-tools/dar.rst

@@ -39,12 +39,9 @@ Currently **dar** supports five different modes to modularize the architecture.
 Each module is seen as a component of the architecture.
 - **file-mode** all functions within a file are put in the same component
 - **map-mode**  a separate map file sorts functions into a component
-- **module-mode** Fortran module definitions are used to place a function into a
-  component
-- **java-class-mode** The simple class name is used for component names and to
-  group functions/methods
-- **java-class-long-mode** The full qualified name of classes is used for
-  component names and to group functions/methods
+- **module-mode** Fortran module definitions are used to place a function into a component
+- **java-class-mode** The simple class name is used for component names and to group functions/methods
+- **java-class-long-mode** The full qualified name of classes is used for component names and to group functions/methods
 
 In principle, it is possible to specify multiple modes. This is helpful when
 for example not all parts of a program use, e.g., Fortran modules, then the

documentation/requirements.txt

@@ -1,6 +1,6 @@
-sphinx==7.2.6
-readthedocs-sphinx-search==0.3.2
-docutils<0.21
-jinja2<3.1
-guzzle_sphinx_theme>=0.7.8,<0.8.0
+sphinx==7.3.7
+readthedocs-sphinx-search==0.3.1
+docutils>=0.21.2
+jinja2>=3.1.3
+guzzle_sphinx_theme>=0.7.11,<0.8.0