renaming user-provided configuration objects so that it's easy to find synchronizer configuration and extensions within your own body of configuration and app context files
package-scoping a lot of synchronizer internals, so that it's clearer how to use this library the way it was intended to be used, at the cost of hiding implementations that an advanced user may want to extend
package scoping this lock registry so that it's clear that syncrhonizer builds these internally, and you don't have to provide them yourself
dropping this spring stereotype to discourage component-scanning this package, because SynchronizerAdviceConfigurationBean is the preferred way to get into the spring app context
renaming the synchronizer advice class, so that it's easier to spot in your stack
renaming the synchronizer lock key so that it's obvious it goes with the synchronizer framework
moving this interface out of the synchronizer package because it's not synchronizer specific
moving some synchronizer framework classes out of the zookeeper package, because they're not zookeeper specific
supporting a more forward compatible configuration strategy, where all you have to do to inject the boilerplate synchronizer beans is component scan this package. that way, if we add any new standalone boilerplate beans in the future, the component scan will pick them up.
Merge branch 'dev'
cleaning up unused dependencies
Merge branch 'dev'
updating the package and class names in the documenation
switching over to use a semver version number. bumping the major number to reflect the backward incompatible api changes