The broker module does not depend on the broker-plugins at compile time, and so its generated pom currently doesn't mention them at all. It does however depend on the management plugins at runtime. We should add the broker plugins as runtime dependencies in the broker pom, with the optional bdbstore modules listed as optional as optional dependencies.
Most of the broker-plugins use 'provided' scope for the broker dependencies for historical reasons relating to their previous osgification (shipping certain deps at the broker level and exporting them, plus needing to place them in a completely different location from the core broker jars). The optional bdbstore module does not, but it would be useful if it aligned with the others and indeed would be good to ensure the optional [non-Apache Licence] BDB JE dependency must be added explicitly in the users pom in addition to the conscious choice to explicitly add the bdbstore module itself in general.