You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@apache.org> on 2017/09/04 13:55:00 UTC

[jira] [Created] (MJAVADOC-494) [REGRESSION] javadoc:aggregate ignores repositories declared in sub-modules

Martin Desruisseaux created MJAVADOC-494:
--------------------------------------------

             Summary: [REGRESSION] javadoc:aggregate ignores repositories declared in sub-modules
                 Key: MJAVADOC-494
                 URL: https://issues.apache.org/jira/browse/MJAVADOC-494
             Project: Maven Javadoc Plugin
          Issue Type: Bug
          Components: javadoc
    Affects Versions: 3.0.0-M1
         Environment: Maven Javadoc plugin 3.0.0-M1
Apache Maven 3.5.0
Java version 1.8.0_144

            Reporter: Martin Desruisseaux


Given a multi-modules project with:

* A {{<repository>… URL A …</repository>}} element in the root {{pom.xml}}.
* Another {{<repository>… URL B …</repository>}} element in the {{pom.xml}} of a module, for downloading a JAR file used only by that specific module (we do that in order to depend only on Maven central for all modules except one).

Then:
* {{mvn install}} works: it download all JAR files as expected.
* {{mvn javadoc:javadoc}} also work with both Maven Javadoc plugin 2.10.4 and 3.0.0-M1.
* {{mvn javadoc:aggregate}} with Maven Javadoc plugin 2.10.4 works.
* {{mvn javadoc:aggregate}} with Maven Javadoc plugin 3.0.0-M1 fails (regression).

Maven Javadoc plugin 3.0.0-M1 execution produces the following logs (simplified in this issue for brevity):

{noformat}
Downloading: URL A/.../MyArtifact.jar
Downloading: https://repo.maven.apache.org/maven2/.../MyArtifact.jar
{noformat}

No download attempt from URL B is found; its {{<repository>}} declaration (in a sub-module) is apparently ignored. Note that the JAR is present in my {{.m2/repository}} directory but is apparently ignored too.

Downgrading Maven Javadoc plugin to 2.10.4 with everything else identical allows successful aggregated Javadoc generation.

*Note:* another user apparently has [the same issue on stack overflow|https://stackoverflow.com/questions/46034250/maven-javadocaggregate-artifacts-could-not-be-resolved].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)