Jersey should have central version management in it's maven pom.xml files and documentation source files. Jersey sources should be able to change dependency versions in a handful of locations - in the root project POMs. All the other poms inheriting from one of the root poms, as well as all the documentation source files should be then referencing the dependency versions via variable properties rather than as absolute numbers. The described approach would reduce the amount of work needed for any subsequent version updates as well as help ensure consistency of any such change.
For example, look for hard coded <version>1.9.36</version> used in:
found in these files:
grizzly version "1.9.36" is also hard coded within these documentation files:
There are many other such instances throughout Jersey code that should be changed.