Keeping Up to Date With Traccar Server Versions While Working from Source Code
If you want to be in sync with master project, you just need to merge all the changes.
ok, but when I do a 'mvn package' it only produces the single JAR file. Where does the content for the other folders/directories (below) come from? What other steps do I need?
bin conf data lib logs tracker-server.jar web
You can take a look at packaging script if you want to know more:
https://github.com/tananaev/traccar/blob/master/setup/package.sh
Anton,
After taking a look at the package.sh script and seeing all the required stuff being looked at for with check_requirement, I believe using this would be overkill for what I need. My custom changes are rolled up in the jar created after running 'mvn pakage'. All I need is to move that jar to my Linux/Centos server, and replace the existing JAR. Additionally, I would need to just use/run your pre-built newer/latest version FIRST to setup/upgrade the environment.
Please let me know if this approach sounds ok?
-Devon
Yes, that's what I would recommend to do. You would need packaging script only if you want to distribute your own version of Traccar.
As you continue to update the 'Traccar Server' and accompanying source code (on Git). What are the required steps to keep my local environment up to date?
I've added some custom code to the source code; ran 'mvn package' and migrate this JAR file to my Linux/CentOS server at this location : '/opt/traccar/tracker-server.jar'. All runs well, however each time a new version is released I go as far as comparing/synchronizing my (Eclipse) workspace and accepting the changes that do not conflict with my custom code, the build the new JAR for deployment. I am concerned that if there are other changes to the Traccar Server environment/structure, outside of this JAR, that I my server environment will no longer be in synch.
Thank you kindly.