Developer builds: can't Enter sightings

After compiling, the “Enter sightings” button puts up an Exception window and no sighting can be entered. Nothing happens on the UI for subsequent presses of the button. The same is true for the “Edit sightings…” button.

The workaround is to place two empty files in model/src/main/resources/: ebirdapikey.txt and googleapikey.txt. Then sightings can be entered, though there will still be exceptions printed on the console and the map functionality won’t work (unless those files contain valid keys).

It would be nice if the exception, README.md or other instructions listed the directory where these files should be placed: I couldn’t tell from the exceptions or code which directory to use.

If updating developer instructions, a note about JDK versions might also be helpful (though maybe all this is obvious to more-experienced Java devs). Neither jdk8 (the available version on my Debian stable system) nor jdk12 (the current Java version) worked: the maven build failed with unhelpful error messages. I downloaded and extracted the deprecated JDK 10 into a temp directory and was able to compile on Linux by setting JAVA_HOME to that jdk10 directory and following the README.md instructions; then using that jdk10 by running $JAVA_HOME/bin/java -jar app/target/app-<version>-SNAPSHOT.jar).

Comments (1)