Databases
StackOverflow2013
Postsdbo
POMaven doesn't recognize sibling modules when running mvn dependency:tree
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
    primarykey
    data
    text
    <p>I'm trying to set up a multi-module Maven project, and the inter-module dependencies are apparently not being set up correctly.</p> <p>I have:</p> <pre class="lang-xml prettyprint-override"><code>&lt;modules&gt; &lt;module&gt;commons&lt;/module&gt; &lt;module&gt;storage&lt;/module&gt; &lt;/modules&gt; </code></pre> <p>in the parent POM (which has a packaging-type pom) and then subdirectories <code>commons/</code> and <code>storage/</code> which define JAR poms with the same name.</p> <p>Storage depends on Commons.</p> <p>In the main (master) directory, I run <code>mvn dependency:tree</code> and see:</p> <pre class="lang-xml prettyprint-override"><code>[INFO] Building system [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ [INFO] [dependency:tree {execution: default-cli}] [INFO] domain:system:pom:1.0-SNAPSHOT [INFO] \- junit:junit:jar:3.8.1:test [INFO] ------------------------------------------------------------------------ [INFO] Building commons [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ [INFO] [dependency:tree {execution: default-cli}] ...correct tree... [INFO] ------------------------------------------------------------------------ [INFO] Building storage [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ Downloading: http://my.repo/artifactory/repo/domain/commons/1.0-SNAPSHOT/commons-1.0-SNAPSHOT.jar [INFO] Unable to find resource 'domain:commons:jar:1.0-SNAPSHOT' in repository my.repo (http://my.repo/artifactory/repo) [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) domain:commons:jar:1.0-SNAPSHOT </code></pre> <p>Why does the dependency on "commons" fail, even though the reactor has obviously seen it because it successfully processes its dependency tree? It should definitely not be going to the 'net to find it as it's right there...</p> <p>The pom for storage:</p> <pre class="lang-xml prettyprint-override"><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;packaging&gt;jar&lt;/packaging&gt; &lt;parent&gt; &lt;artifactId&gt;system&lt;/artifactId&gt; &lt;groupId&gt;domain&lt;/groupId&gt; &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt; &lt;/parent&gt; &lt;groupId&gt;domain&lt;/groupId&gt; &lt;artifactId&gt;storage&lt;/artifactId&gt; &lt;name&gt;storage&lt;/name&gt; &lt;url&gt;http://maven.apache.org&lt;/url&gt; &lt;dependencies&gt; &lt;!-- module dependencies --&gt; &lt;dependency&gt; &lt;groupId&gt;domain&lt;/groupId&gt; &lt;artifactId&gt;commons&lt;/artifactId&gt; &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt; &lt;/dependency&gt; &lt;!-- other dependencies --&gt; &lt;dependency&gt; &lt;groupId&gt;junit&lt;/groupId&gt; &lt;artifactId&gt;junit&lt;/artifactId&gt; &lt;version&gt;3.8.1&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/project&gt; </code></pre> <p>Thanks for any suggestions!</p> <p>(Edit)</p> <p>To clarify, what I am looking for here is this: I don't want to have to install module X to build module Y which depends on X, given that both are modules referenced from the same parent POM. This makes intuitive sense to me that if I have two things in the same source tree, I shouldn't have to install intermediate products to continue the build. Hopefully my thinking makes some sense here...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAndré Gasser
    1. USSteven Schlansker
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. USBostone
      1. VTFavorite
    2. VO
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. USmetamatt
      1. VTFavorite
    1. COAhhh, The edit is perfect. Why didn't you write this in the first intention? Also, maybe consider changing the title :) I don't mean to be picky, this is just for the sake of clarity and classification. This will help the whole community in the future when searching for a similar issue (which is not crystal clear with the actual title and content that is about dependency:tree)
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. USPascal Thivent
    2. COHi. Did you find the solution? I have this problem too :(
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. USHai Minh Nguyen
    3. CODoes compilation fail, or just the dependency:tree goal alone? See Don Willis' answer.
      singulars
      1. POMaven doesn't recognize sibling modules when running mvn dependency:tree
      1. USmetamatt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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