The cache manager (cmanager) is a Java-based program which is able to manage GPX files and synchronize geocache logs from Geocaching.com to Opencaching.de. It therefore loads a GPX file with the users cache founds (e.g. myfounds.gpx). After configuring an OKAPI token in the settings, the user is able to match his/her founds against caches listed on Opencaching.de.
Further information in German:
Note: If cmanager fails with an exception, you should try to update your local Java installation to the latest version at first. This especially holds true for SSL errors, but might cause other problems as well.
Important note: This application tries to support you with logging duplicates as best as possible. The results might be wrong due to the used heuristics, so you might end up with multiple results for one GC cache or no results at all. There is no guarantee that the results are correct, so you should be careful with logging by ensuring that this actually is a valid duplicate. (This is one of the reasons for not automating the synchronization by providing some batch processing for sending the actual logs.)
cmanager is distributed under the terms of The GNU General Public License v3. The sources are available on GitHub.
This version is a fork of the original repository by Samsung1. While the original version discontinued support for the log transfer functionality itself, this fork tries to keep it working. Additionally some problems of the original version have been fixed.
Releases are published on GitHub as "Releases".
Besides the regular release, there is a pre-release as well. This will be built by GitHub Actions on every change to the master branch. Please note that these files (named cm-<hexStringOfTheCommit>.jar) are development versions which might have additional bugs or provide undocumented changes/features. Use them at your own risk!
- Java development kit (JDK) in version >= 10. The minimum required Java version to run the application is Java 8 nevertheless, but the
Compatibility.javafile depends on a method introduced in Java 10. - You need to provide API keys for compiling
cmanager. See next section for details.
Request your personal API keys for the supported OpenCaching sites, currently:
Copy templates/oc_okapi.properties to the root directory of the Git repository. Then edit oc_okapi.properties and insert your keys.
Run gradle build from the root directory of the Git repository (or use ./gradlew build if you do not have Gradle installed locally).
To create a JAR file, run gradle jar (or ./gradlew jar). The JAR file will be located in build/libs.
There is experimental support for bundling the application in a way that no local Java installation is needed for executing it.
To create the corresponding image, run gradle jpackageImage (or ./gradlew jpackageImage). The image will be available inside the build/jpackage/cmanager directory. You might want to put this directory into a dedicated archive file for redistribution using the jpackageImageZip task. Please note that this an incubating feature of Java 14, so at least Java 14 is required and this feature might break due to API changes.
- Java in version >= 8. I recommend you to use at least Java 10. If you use the
jpackageimage, no own Java installation is needed.
Run gradle run (or ./gradlew run) from the root directory of the Git repository.
Run java -jar cm-0.1.2.jar from the directory containing the JAR file. Replace 0.1.2 with the corresponding version number.
Double-click on cmanager.exe (on Windows) from the directory containing this package. Please note that this version is not being distributed in the release section at the moment.