Databases
StackOverflow2013
Postsdbo
POMaven Javadoc aggregate-jar plugin fails because of unresolved dependencies
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMaven Javadoc aggregate-jar plugin fails because of unresolved dependencies
    primarykey
    data
    text
    <p>I have multi-module Maven project in which I run the maven-javadoc-plugin to generate javadoc. In my parent pom.xml I have defined the plugin build as follows:</p> <pre><code>&lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-javadoc-plugin&lt;/artifactId&gt; &lt;version&gt;2.9.1&lt;/version&gt; &lt;configuration&gt; &lt;!-- Default configuration for all reports --&gt; &lt;/configuration&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;aggregate&lt;/id&gt; &lt;goals&gt; &lt;goal&gt;aggregate-jar&lt;/goal&gt; &lt;/goals&gt; &lt;phase&gt;install&lt;/phase&gt; &lt;configuration&gt; &lt;!-- Specific configuration for the aggregate report --&gt; &lt;/configuration&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; </code></pre> <p>When I run <code>mvn clean install</code> the build fails with unresolved dependencies, but I see the following warning:</p> <blockquote> <p>[WARNING] The dependency: [my.application:my-module:jar:1.7.1] can't be resolved but has been found in the reactor (probably snapshots). This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install.</p> </blockquote> <p>As I am currently building my-module 1.7.1, I would assume Maven to detect this and run the aggregate-jar after building my-module, but for some reason it expects my-module to already be installed in a repo. </p> <p>My Maven version is 3.0.4. Please keep in mind that I am new to Maven builds so this may be a very simple question, but I was not able to find any answer. </p> <p>Some observations:</p> <ul> <li>The build succeeds if I first run <code>mvn clean install</code> without the javadoc plugin <code>aggregate-jar</code> goal</li> <li>The javadoc plugin <code>aggregate</code> goal runs fine.</li> <li>This <a href="http://jira.codehaus.org/browse/MNG-4618">bug</a> refers exactly to my issue, but should have been solved in Maven 3 (2010)</li> </ul>
    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. USqtips
    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. VO
      singulars
      1. POMaven Javadoc aggregate-jar plugin fails because of unresolved dependencies
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe [last comment](http://jira.codehaus.org/browse/MNG-4618?focusedCommentId=318031&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-318031) in the maven bug you reference MNG-4618 is from someone who states that the bug has not been fixed (or has reappeared) - you might want to specifically reopen that bug and state that you are also having the problem. The user states the following "I can ONLY successfully aggregate JavaDocs by removing the <executions> and calling `mvn package javadoc:aggregate-jar` instead." - you could give that a try.
      singulars
      1. POMaven Javadoc aggregate-jar plugin fails because of unresolved dependencies
      1. USDB5
    2. COI assumed that using javadoc aggregate-jar goal in a multimodule project would be very commonly used operation, so I was unsure whether I am doing stuff the right way. I try to follow your suggestions of reopening the bug, but I do not have the permissions to alter the maven command as it is used in a shared build job. EDIT: To reopen or comment on the bug I need access to Codehaus Jira, and that I have to request from an administrator. Is there an easier way to submit my info to that case/bug?
      singulars
      1. POMaven Javadoc aggregate-jar plugin fails because of unresolved dependencies
      1. USqtips
 

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