Update URLs to new gitlab instance

etc/doxygen/pages/HowTos.dox

@@ -85,7 +85,7 @@ With the corresponding configuration in ./config/Armar3Config.cfg:
 
 \section RobotAPI-HowTos-RobotViewer How to inspect the robot's structure 
 
-Robots are usually defined in the Simox XML (https://gitlab.com/Simox/simox/wikis/FileFormat) or in the URDF format. To inspect the kinematic structure, visualizations and physical properties, you can use the <i>RobotViewer</i> tool which is part of the Simox library. In particlular you can visualize all coordinate frames that are present in the robot defintion.
+Robots are usually defined in the Simox XML (https://git.h2t.iar.kit.edu/sw/simox/simox/-/wikis/FileFormat) or in the URDF format. To inspect the kinematic structure, visualizations and physical properties, you can use the <i>RobotViewer</i> tool which is part of the Simox library. In particlular you can visualize all coordinate frames that are present in the robot defintion.
 Start it with the following command:
 \code
     RobotViewer --robot path/to/robot.xml
@@ -96,7 +96,7 @@ Start it with the following command:
 \section RobotAPI-HowTos-RemoteRobot-Access How to access a RobotStateComponent
 
 The RobotStateComponent provides several methods for accessing the current configuration of the robot and for getting a snapshot of the current state which is compatible with
-models of the Simox/VirtualRobot framework. With these models the whole functionality of Simox (https://gitlab.com/Simox/simox) can be used, e.g. IK solving, collision detection or motion and grasp planning.
+models of the Simox/VirtualRobot framework. With these models the whole functionality of Simox (https://git.h2t.iar.kit.edu/sw/simox/simox) can be used, e.g. IK solving, collision detection or motion and grasp planning.
 
 See also \ref RobotAPI-RemoteRobot-Overview.
 \par Creating a synchronized model (RemoteRobot)

etc/doxygen/pages/Tutorials.dox

@@ -8,6 +8,6 @@ Tutorials related to RobotAPI:
 
 \li  \ref Component-ArVizExample (Example component for how to use ArViz)
 
-\li  <a href="https://gitlab.com/ArmarX/meta/Academy/-/tree/master/tutorials/100_beginner/301_memory_server_and_client_tutorial_cpp">Memory Server and Client Tutorial</a>
+\li  <a href="https://git.h2t.iar.kit.edu/sw/armarx/meta/academy/-/tree/master/tutorials/100_beginner/301_memory_server_and_client_tutorial_cpp">Memory Server and Client Tutorial</a>
 
 */

etc/doxygen/pages/armarpose.dox

@@ -23,7 +23,8 @@ Use this variable if you specify global poses and an empty Agent-string. Empty f
 \section FramedPose-FramedPositionCreation Creation of new FramedPositions
 To create a new FramedPosition (FramedOrientation, FramedVector and FramedPose work analogously) one needs
 to know the position, the coordinate frame name and the agent name.
-The coordinate frame is usually the name of the RobotNode, e.g. the tcp of the robot. All nodes of a robot can be inspected with the <a href="https://gitlab.com/Simox/simox/wikis/Examples">Simox tool *RobotViewer*</a>.
+The coordinate frame is usually the name of the RobotNode, e.g. the tcp of the robot.
+All nodes of a robot can be inspected with the <a href="https://git.h2t.iar.kit.edu/sw/simox/simox/-/wikis/Examples">Simox tool *RobotViewer*</a>.
 The agent name can be retrieved via the \ref armarx::RobotStateComponent like this:
 
 \code

source/RobotAPI/components/RobotState/RobotStateComponent.h

@@ -59,7 +59,7 @@ namespace armarx
     /**
      * \defgroup Component-RobotStateComponent RobotStateComponent
      * \ingroup RobotAPI-Components
-     * \brief Maintains a robot representation based on VirtualRobot (see [Simox](http://gitlab.com/Simox/simox)).
+     * \brief Maintains a robot representation based on VirtualRobot (see [Simox](https://git.h2t.iar.kit.edu/sw/simox/simox)).
      *
      * The robot can be loaded from a Simox robot XML file.
      * Upon request, an Ice proxy to a shared instance of this internal robot

source/RobotAPI/libraries/ArmarXObjects/ObjectFinder.h

@@ -18,8 +18,7 @@ namespace armarx
     /**
      * @brief Used to find objects in the ArmarX objects repository [1] (formerly [2]).
      *
-     * @see [1] https://gitlab.com/ArmarX/PriorKnowledgeData
-     * @see [2] https://gitlab.com/ArmarX/ArmarXObjects
+     * @see [1] https://git.h2t.iar.kit.edu/sw/armarx/prior-knowledge-data
      */
     class ObjectFinder : Logging
     {