Module Hierarchy Question

[Ashley Yakeley]

Is it wrong or discouraged to have both modules "A.B" and "A.B.C"? For 
instance, I want to create a number of modules:

    Org.Org.Semantic.HBase.Basic.Trivial
    Org.Org.Semantic.HBase.Basic.Logic
    Org.Org.Semantic.HBase.Basic.Equivalence
    Org.Org.Semantic.HBase.Basic.Type
    etc.

... and then have a single module that collects them all up:
     
    module Org.Org.Semantic.HBase.Basic
        (
        module Org.Org.Semantic.HBase.Basic.Trivial,
        module Org.Org.Semantic.HBase.Basic.Logic,
        module Org.Org.Semantic.HBase.Basic.Equivalence,
        module Org.Org.Semantic.HBase.Basic.Type,
        etc.
        ) where
        {
        import Org.Org.Semantic.HBase.Basic.Trivial;
        import Org.Org.Semantic.HBase.Basic.Logic;
        import Org.Org.Semantic.HBase.Basic.Equivalence;
        import Org.Org.Semantic.HBase.Basic.Type;
        etc.
        }



-- 
Ashley Yakeley, Seattle WA