Metacat

do not shutdown hazelcast -- it needs to be running after the upgrade process so that Metacat actually works.
I think the newer version of HZ makes it so the threads are all released as needed.
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5572

Commenting out the parts of the upgrade script that started to refer to EXID. At this point, the registration of EZID identifiers will be done out-of-band with respect to the upgrade.

use plain String parameter for {pid} instead of XML serialization of it.

remove {pid} from POST URL on CN.registerSystemMetadata()
https://redmine.dataone.org/issues/2284

remove {pid} from POST URL on CN.create()
https://redmine.dataone.org/issues/2284

remove {pid} from POST URL on MN.create()
https://redmine.dataone.org/issues/2284

catch cases where the previous/next revision of objects have not had system metadata generated yet

create system metadata object if it wasn't found in HZ

process systemMetadata from the docInfo string before writing to the database so that we guarantee guid-docid mapping exists before attempting to look it up.

upgrade to hazelcast 1.9.4.6 so that threadpools are released when not needed (http://code.google.com/p/hazelcast/issues/detail?id=765).
include ant target to run a specific main class (mostly for debugging)