Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't have a direct answer to the question. But using some kind of "module path" as naming convention for the <code>&lt;name&gt;</code> of my modules works for me. As you'll see, this convention is self explaining. </p> <p>Given the following project structure:</p> <pre> . ├── pom │   ├── pom.xml │   └── release.properties ├── pom.xml ├── samples │   ├── ejb-cargo-sample │   │   ├── functests │   │   │   ├── pom.xml │   │   │   └── src │   │   ├── pom.xml │   │   └── services │   │   ├── pom.xml │   │   └── src │   └── pom.xml └── tools ├── pom.xml └── verification-resources ├── pom.xml └── src </pre> <p>Here is the output of a reactor build:</p> <pre> $ mvn compile [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Personal Sandbox - Samples - Parent POM [INFO] Personal Sandbox - Samples - EJB3 and Cargo Sample [INFO] Personal Sandbox - Tools - Parent POM [INFO] Personal Sandbox - Tools - Shared Verification Resources [INFO] Personal Sandbox - Samples - EJB3 and Cargo Sample - Services [INFO] Personal Sandbox - Samples - EJB3 and Cargo Sample - Functests [INFO] Sandbox Externals POM ... </pre> <p>This gives IMHO a very decent overview of what is happening, scales correctly, and it's pretty easy to find any module in the file system in case of problems.</p> <p>Not sure this does answer all your needs though.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload