You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So when I try to compile your project using Maven, I get my *.war file but when I try to run it on the server, it gets stuck on "Loading application...".
It also seems like the web page is trying to load files which seem to be missing in my *.war file:
GET http://my.ip/traccar/reset.css 404 (Not Found)
(index):29 GET http://my.ip/traccar/traccar.nocache.js 404 (Not Found)
(index):21 GET http://my.ip/traccar/reset.css 404 (Not Found)
(index):29 GET http://my.ip/traccar/traccar.nocache.js 404 (Not Found)
I unzipped the war file and there's no traccar folder.
So I put the traccar folder from your war file in mine and voila, it's working fine. But the problem is that it's ignoring all my changes that I did to the source code. Maybe it's using a cached version? (I tried using other devices and also removed local cache, nothing helped).
I'm running Traccar 3.9 on a Debian 8.
EDIT: I just checked the traccar folder and it seems like there are *.cache.js files mapped in compilation-mappings.txt. Maybe that's causing the issue?
The text was updated successfully, but these errors were encountered:
So when I try to compile your project using Maven, I get my *.war file but when I try to run it on the server, it gets stuck on "Loading application...".
It also seems like the web page is trying to load files which seem to be missing in my *.war file:
I unzipped the war file and there's no traccar folder.
So I put the traccar folder from your war file in mine and voila, it's working fine. But the problem is that it's ignoring all my changes that I did to the source code. Maybe it's using a cached version? (I tried using other devices and also removed local cache, nothing helped).
I'm running Traccar 3.9 on a Debian 8.
EDIT: I just checked the traccar folder and it seems like there are *.cache.js files mapped in compilation-mappings.txt. Maybe that's causing the issue?
The text was updated successfully, but these errors were encountered: