handle situation when minerva.war was not exploded by tomcat

CHANGELOG

 minerva (15.0.3) stable; urgency=medium
   * Bug fix: caching chemicals/drug data on big map could cause Out of Memory
     issues (#1315)
+  * Bug fix: when there is a problem with minerva deployment on tomcat proper
+    warning message is presented in admin panel (#1332)
 
  -- Piotr Gawron <piotr.gawron@uni.lu>  Wed, 8 Jul 2020 16:00:00 +0200
 

frontend-js/src/main/js/Admin.js

@@ -163,11 +163,15 @@ Admin.prototype.checkAvailableVersion = function () {
   var self = this;
 
   var localVersion = semver.coerce(self.getConfiguration().getVersion());
-  return self.getLatestPublishedVersion().then(function (publishedVersion) {
-    if (semver.gt(publishedVersion, localVersion) > 0) {
-      GuiConnector.warn("New minerva version (" + publishedVersion + ") was released. Please upgrade your minerva instance or contact system administrator to do so.");
-    }
-  });
+  if (localVersion === null) {
+    GuiConnector.warn("Minerva was not deployed properly. Please contact system administrator.");
+  } else {
+    return self.getLatestPublishedVersion().then(function (publishedVersion) {
+      if (semver.gt(publishedVersion, localVersion) > 0) {
+        GuiConnector.warn("New minerva version (" + publishedVersion + ") was released. Please upgrade your minerva instance or contact system administrator to do so.");
+      }
+    });
+  }
 };
 
 /**