This is something that the productization process has to handle: the modeshape dependency graph for the modeshape-jdbc module contains:
[INFO] | \- org.apache.httpcomponents:httpclient:jar:4.2.1:compile (version managed from 4
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.2.1:compile
[INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile (version managed from 1.1
[INFO] | \- commons-codec:commons-codec:jar:1.4:compile (version managed from 1.6)
So the jar must be taken out during the productization process.
Randall Hauch <firstname.lastname@example.org> updated the status of jira MODE-2262 to Resolved
Rejecting, because this is not a ModeShape issue. The productization process is excluding this jar. See JIRA for more details.
IMO this should be assigned to prod and then re-acked.
Fixed with commit a282b1f779d8356adc786612467fa5202f2aedca of rpms/modeshape.git:
Restore commons-logging so that the client jar can be used standalone.