Databases
StackOverflow2013
Postsdbo
PONon-resolvable parent POM: When building Maven 3 Project Site
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONon-resolvable parent POM: When building Maven 3 Project Site
    primarykey
    data
    text
    <p>I am currently facing the following problem with Maven 3 when I am trying to build the site. I will appreciate you help on this.</p> <p><em>mvn clean site</em></p> <pre><code>.......... [INFO] Reactor Summary: [INFO] [INFO] Project A ......................................... SUCCESS [15.383s] [INFO] Project B ......................................... SUCCESS [2.232s] [INFO] My Site ........................................... FAILURE [0.105s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 24.769s [INFO] Finished at: Fri Jun 29 14:26:04 AMT 2012 [INFO] Final Memory: 18M/150M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.1:site (default-site) on project site: SiteToolException: Unable to read local module-POM: 1 problem was encountered while building the effective model for my.com:projA:0.1-SNAPSHOT [ERROR] [FATAL] Non-resolvable parent POM: Could not find artifact my.com:parent-pom:pom:0.1-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 12, column 13 [ERROR] for project my.com:projA:0.1-SNAPSHOT ............. </code></pre> <p><strong>First here is the configuration:</strong></p> <pre><code>Apache Maven 3.0.4 (r1232337; 2012-01-17 12:44:56+0400) Java version: 1.7.0_04, vendor: Oracle Corporation Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac" Nexus repository: 2.0.6 </code></pre> <p><strong>The parent POM:</strong></p> <pre><code>&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;name&gt;Parent POM&lt;/name&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;parent-pom&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;packaging&gt;pom&lt;/packaging&gt; &lt;build&gt; &lt;pluginManagement&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-site-plugin&lt;/artifactId&gt; &lt;version&gt;3.1&lt;/version&gt; &lt;configuration&gt; &lt;reportPlugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-project-info-reports-plugin&lt;/artifactId&gt; &lt;version&gt;2.4&lt;/version&gt; &lt;/plugin&gt; &lt;/reportPlugins&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/pluginManagement&gt; &lt;/build&gt; </code></pre> <p><strong>The aggregation project pom:</strong></p> <pre><code>&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;name&gt;My Site&lt;/name&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;site&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;packaging&gt;pom&lt;/packaging&gt; &lt;parent&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;parent-pom&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;relativePath/&gt; &lt;/parent&gt; &lt;modules&gt; &lt;module&gt;projA&lt;/module&gt; &lt;module&gt;projB&lt;/module&gt; &lt;/modules&gt; </code></pre> <p><strong>The pom of Project A:</strong></p> <pre><code>&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;name&gt;Project A&lt;/name&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;projA&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;parent&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;parent-pom&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;relativePath/&gt; &lt;/parent&gt; </code></pre> <p><strong>The pom of Project B:</strong></p> <p>4.0.0</p> <pre><code>&lt;name&gt;Project B&lt;/name&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;projB&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;parent&gt; &lt;groupId&gt;my.com&lt;/groupId&gt; &lt;artifactId&gt;parent-pom&lt;/artifactId&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;relativePath/&gt; &lt;/parent&gt; </code></pre> <p><strong>Here is the structure of the folder where I run "mvn clean site":</strong></p> <pre><code>./pom.xml (aggregation project) ./projA/pom.xml (Project A) ./projB/pom.xml (Project B) </code></pre> <p>parent-pom is successfully deployed to NEXUS repository before the execution of <code>mvn clean site</code> with following command <code>mvn deploy -DaltDeploymentRepository=snapshots::default::http://MyServer:8081/nexus/content/repositories/snapshots</code></p> <p><strong>And finally the problem itself:</strong></p> <p>When I run <code>mvn clean site</code> right after the deployment of parent-pom site is built successfully. If I delete the folder (with its content) "my" (it contains the parent-pom) from the local repository (~/.m2/repository) and then try to build the site with <code>mvn clean site</code> I am getting the error described at the beginning. Actually Maven downloads the parent-pom from the NEXUS. I have compared the downloaded files and files which have been generated after the deployment and have realized that few are missing, for instance maven-metadata-local.xml near to "0.1-SNAPSHOT" folder.</p> <p>So when I am trying to run the site building job from Jenkins I am getting the error described above, because the parent-pom is not deployed from the machine where Jenkins run.</p> <p>How can I come up with this problem or what I did wrong?</p> <p>Thank you.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStgrigoryan
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. USDon Walling
      1. VTFavorite
    2. VO
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. USIdcmp
      1. VTFavorite
    3. VO
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would remove the relativePath entry of your modules, cause it's empty so its not needed. Can you enhance the picture with the folder structure where your parent pom is located? And why are the parent pom and the aggregation pom are different ones ?
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. USkhmarbaise
    2. CO<relativePath/> forces maven to download parent POM from the repository, instead of looking it up in the structure. If I remove it maven shows warnings because it starts to think that the parent is in ../pom.xml, which is not true. Regarding the aggregation and inheritance. It is OK to have different parent and aggregation POMs. Here is the link: [Aggregation vs Inheritance](http://maven.apache.org/pom.html#Inheritance_v)
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. UStgrigoryan
    3. COI know that's possible having different aggregator and parentbut it makes life not easier.
      singulars
      1. PONon-resolvable parent POM: When building Maven 3 Project Site
      1. USkhmarbaise
 

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