Brian Hatchl

Revert the error message changes and I'll approve :neckbeard:

I have a branch https://github.com/ngageoint/hootenanny/tree/5339_filtered_cut_replace where I've added incomplete parents (mostly relations) to the reference pull. This should make them available to hoot for removing the member ref when the...

@bmarchant @mschicker Can we put our :brain: together and see if the incomplete relation behavior can be changed?

@mattjdnv you too

I think changes to ConfigOptions.asciidoc only get picked up at build time. There are a set of conf files under `core/conf` that can be updated to override default parameter values...

I believe that when the Hoot command process accesses JNI that is a separate jvm from the one used by tomcat. The conf file is passed as an argument to...

In the `v11.0.0` build of ME_JOSM we added an explicit `area=yes` or `area=no` to the presets for any FCODE that can be both a Line and an Area. https://github.com/ngageoint/hootenanny/pull/5189 This...

I can reproduce this. Will work with @mattjdnv to get the FCODE preserved round-trip.

Interestingly, if I go to Preferences... Nome Preferences... and uncheck "Drop defaults", the processing facility FCODE is preserved like @MikeTho16 experienced. I think we want this setting (uncheck "Drop defaults")...

So the upshot is the translation server clients need to send "full" relations to get the proper behavior? I'm pretty sure I set the test up with exactly what's being...