[DOC] fixed links to old website

src/modules/navigationSlices/resources/META

@@ -82,7 +82,7 @@
     // Optional description for a resource
     description ="First Steps Tutorial, showing the first steps to take with OpenWalnut.";
     // The URL. Required.
-    url="http://redmine.openwalnut.org/projects/openwalnut/wiki/FirstSteps";
+    url="https://bsvgit.informatik.uni-leipzig.de/openwalnut/openwalnut/wikis/FirstSteps";
   };
   // Multiple online resources allowed.
   online

src/modules/template/WMTemplate.cpp

@@ -33,7 +33,7 @@
 /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
 // How to create your own module in OpenWalnut? Here are the steps to take:
 //   * Setup your module building framework
-//     * See http://redmine.openwalnut.org/projects/openwalnut/wiki/Module_ExternalDevelopment for details
+//     * See https://bsvgit.informatik.uni-leipzig.de/openwalnut/openwalnut/wikis/Module_ExternalDevelopment for details
 //   * copy the template module directory
 //   * think about a name for your module
 //   * rename the files from WMTemplate.cpp and WMTemplate.h to WMYourModuleName.cpp and WMYourModuleName.h
@@ -414,7 +414,7 @@ void WMTemplate::moduleMain()
     // that your thread misses the event. The resettable flag for those condition sets can help here. Whenever a condition, managed by the
     // condition set, fires, the moduleState variable remembers it. So, the next call to m_moduleState.wait() will immediately return and reset
     // the "memory" of the moduleState. For more details, see:
-    // http://redmine.openwalnut.org/projects/openwalnut/wiki/MultithreadingHowto#How-to-wait-correctly
+    // https://bsvgit.informatik.uni-leipzig.de/openwalnut/openwalnut/wikis/MultithreadingHowto#how-to-wait-correctly
 
     // Most probably, your module will be a module providing some kind of visual output. In this case, the WGEManagedGroupNode is very handy.
     // It allows you to insert several nodes and transform them as the WGEGroupNode (from which WGEManagedGroupNode is derived from) is also

src/modules/template/resources/META

@@ -157,7 +157,7 @@
     // Optional description for a resource
     description ="First Steps Tutorial, showing the first steps to take with OpenWalnut.";
     // The URL. Required.
-    url="http://redmine.openwalnut.org/projects/openwalnut/wiki/FirstSteps";
+    url="https://bsvgit.informatik.uni-leipzig.de/openwalnut/openwalnut/wikis/FirstSteps";
   };
   // Multiple online resources allowed.
   online

src/qtgui/WApplication.cpp

@@ -33,7 +33,7 @@
 #include "core/common/WException.h"
 #include "core/common/WLogger.h"
 
-#define OPENWALNUT_BUGREPORTER_URL "http://redmine.openwalnut.org/projects/openwalnut/issues"
+#define OPENWALNUT_BUGREPORTER_URL "https://bsvgit.informatik.uni-leipzig.de/openwalnut/openwalnut/issues"
 
 WApplication::WApplication( int &argc, char** argv, bool GUIenabled ) // NOLINT
     : QApplication( argc, argv, GUIenabled )

src/qtgui/WMainWindow.cpp

@@ -278,7 +278,7 @@ void WMainWindow::setupGUI()
     m_permanentToolBar = new WQtToolBar( "Standard Toolbar", this );
     addToolBar( Qt::TopToolBarArea, m_permanentToolBar );
 
-    // math: Due to this issue: http://redmine.openwalnut.org/issues/406 resp.
+    // math: Due to the OLD issue 406 resp.
     // http://stackoverflow.com/questions/31983269/how-to-identify-a-certain-qt-widget
     // There might be a white box, on Apple Mac OSX only, which sometimes hides the window buttons
     // for maximization, minimization and closing. This is extremely disturbing, hence, we leave them
@@ -547,7 +547,7 @@ void WMainWindow::setCompatiblesToolbar( WQtCombinerToolbar* toolbar )
              m_currentCompatiblesToolbar, SLOT( setToolButtonStyle( Qt::ToolButtonStyle ) ) );
 
     // and the position of the toolbar
-    // math: Due to this issue: http://redmine.openwalnut.org/issues/406 resp.
+    // math: Due to the OLD issue 406 resp.
     // http://stackoverflow.com/questions/31983269/how-to-identify-a-certain-qt-widget
     // There might be a white box, on Apple Mac OSX only, which sometimes hides the window buttons
     // for maximization, minimization and closing. This is extremely disturbing, hence, we leave them
@@ -701,7 +701,7 @@ QString collectFilters()
         result += description + QString( "(*" ) + extension + QString( ");;" );
     }
 
-    // math: on 11. Aug. 2015, related issue: http://redmine.openwalnut.org/issues/404
+    // math: on 11. Aug. 2015, related old issues 404
     // The following #ifdef is due to the following QT-Bug: https://bugreports.qt.io/browse/QTBUG-38303
     // Hence, we use any file as known file type for MAC OSX only.
     #ifdef Q_OS_OSX