How to include the modules in a top-level POM in another project?

Question

I've googled and stack-overflowed everything, but maybe not enough as I'm still not clear how one adds a module of a Maven project as a dependency in another.

So for example let's say we've got:

MajorPager
  |___ POM.xml
  |___ chuck-commons-core
  |    |____POM.xml
  |____rajni-commons-core
       |____POM.xml

Now I want to add chuck-commons-core but not rajni-commons-core. If I do it directly, it can't find the module. So I ran across the following discussions on stack-overflow and my old friend Guggal:

In summary, the below discussions talk of how to create multi-module projects but not really how to include the sub-modules in a top-level POM into another project.

Useful discussions for context

• SO Adding a reference to a parent POM project
• SO How to add a parent POM as dependency to a different maven project
• SO Adding a reference to Parent POM
• SO Maven Parent POM vs Modules POM
• SO Depend on multi-module aggregator project
• SO How to add dependency in Eclipse?
• SO How do I configure Maven multi-module-dependency on sub project with different package?
• SO How to add a module in parent projects POM as dependency?
• SO How to add a dependency in Maven?
• Maven dependency mechanism
• Maven POM aggregation
• Baeldung Multi-module project
• Codetab Maven multi-module
• Howtodoinjava Maven parent child POM example
• Mastertheboss Maven multi-module tutorial
• Codetab Multi-module hierarchical project
• Sonatype How to share resources across projects
• Spring Multi-module project

Concretely, I'd just like a summary from an expert how they add a sub-module of a Parent POM as a dependency to another project.

Answer 1

As of now, I think this is the best solution - to add the following ccodee to the POM.xml of the MajorPager.

Code block 1 incoming

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.teachme.how</groupId>
            <artifactId>MajorPager</artifactId>
            <version>0.6-SNAPSHOT</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

Code block 2 incoming

<dependencies>
    ...
    <dependency>
        <groupId>com.teachme.how</groupId>
        <artifactId>norris-commons-core</artifactId>
        <version>0.6</version>
    </dependency>
    ...
</dependencies>

When you do so enables Maven to find out where the dependency are - and so Maven picks them up with mvn clean -U install or mvn package -U -DskipTests. And I should like to be educated if this isn't the most effective pattern. Or if any of the fields above are optional that Maven doesn't want me to specify because it can derive it on it's own (say for example, version tag?) - please let me know if that's case as well.