(I am aware that this project is a target of an opaque software generation process, so creating a PR against generated code, strictly speaking, cannot succeed, and I have no expectation that this would be "merged", since that is a meaningless concept in this repository. I do this here to hopefully illustrate the kinds of changes that need to be made internally in some source control system prior to whatever process it is that ultimately produces the source code found in this Github repository. Hopefully some developer can take the changes and the diffs in this PR and apply them appropriately to whatever internal repository ultimately produces this one.)

This PR:

• manages dependency versions properly
• removes useless dependencies
• removes scopes from <dependencyManagement> children which is an antipattern
• moves certain dependencies into the projects that actually use them
• removes various dependency stanzas in subprojects that indicate that the underdocumented Maven dependency management system was not fully understood (understandably!)
• as a side effect ends up producing a list of external dependencies in the <properties> stanza of the root pom.xml
• reduces dependencies, i.e. a dependency on foo-client may actually really only need to be a dependency on foo-core

Broadly speaking: the PR implements proper Maven dependency management, which seems to be what was desired throughout the project, while making it exceedingly clear exactly which external libraries are required by exactly which subprojects.

See:

• bmc-shaded-full is strange #387
• resteasy-client-configurator seemingly only needs a dependency on resteasy-core #386
• Spurious dependencies in bmc-encryption #385
• json-smart seems to be in the wrong project; should probably move from bmc-common to bmc-encryption #384
• bmc-circuitbreaker depends on Jersey but doesn't need to #382

Signed-off-by: Laird Nelson ljnelson@gmail.com