Red Hat Bugzilla – Bug 1316078
Document why rh-mongodb32-runtime depends on rh-java-common packages
Last modified: 2016-05-04 10:36:23 EDT
Description of problem:
rh-mongodb32-runtime depends on rh-java-common packages, I think it is not necessary and the dependencies should be somewhere else, -build subpackage? maybe even mongo-java-driver if it is needed.
Version-Release number of selected component (if applicable):
rh-mongodb32-runtime depends on rh-java-common to be able to enable scl_java_common SCL by enabling rh-mongodb32 SCL - "scl enable rh-mongodb32"
This is a resolution of bug #1129287 from mongodb24 SCL. To be able to do "scl enable rh-mongodb32 -- build-jar-repository /tmp mongo"
Or shouldn't this be supported?
Oh, I haven't realized that, thank you for explaining. Then I think we should just add a comment into the SPEC file so we are clear about why it is done this way.
This fix (dependency) is from mongodb24 era.
Should "If mongodb24 is made to depend on it too then just installing rh-common-java-javapackages-tools will "fix" build-jar-repository and other related tools. If collections want to have the feature of workning build-jar-repository (et al.) then they can add dependency on rh-common-java-javapackages-tools." (bug 1129287, comment 18) be supported also for rh-mongodb32?
Or is updated workaround "scl enable maven30 mongodb24 -- build-jar-repository /tmp mongo" (bug 1129287, comment 17) enough for rh-mongodb32?
What "java functions and tools" should be enabled/functional only by enabling rh-mongodb32 collection?
Mikolaj, what is a current status of build-jar-repository please? Should this collection still depends on rh-java-common-javapackages-tools?
By design, any SCL must be enabled prior to using it, build-jar-repository and other related tools will only look for JARs from enabled collections. If you want out-of-the-box support for build-jar-repository in mongodb24 after installing (and enabling) it then dependency or rh-java-common-runtime is necessary and it's not planned to be changed.
The dependency is documented generally in the Release Notes, no details are relevant for customers.