maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny (JIRA) <>
Subject [jira] (MJAVADOC-116) Impossible to aggregate javadoc if snapshot never built
Date Mon, 20 Aug 2012 22:12:22 GMT


Emmanuel Lécharny commented on MJAVADOC-116:

The problem is that for some reason, the Javadoc plugin is run *before* the other projects
are built, therefore as the associated jars are not present in the ocal .m2 repository.

For instance, while trying to release MINA, the version of each project is bumped up from
XXX-SNAPSHOT to XXX, so the associated jars are not present before the end of the build. Sadly,
the javadoc plugin is trying to fetch those jars, with no success.

If I do a mvn clean install just after the release:prepare, the a second run of the mvn release:prepare
now works.

This is a real problem...
> Impossible to aggregate javadoc if snapshot never built
> -------------------------------------------------------
>                 Key: MJAVADOC-116
>                 URL:
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Damien Lecan
>            Assignee: Vincent Siveton
>         Attachments: clean javadoc-plugin-test-case with classifier, javadoc-plugin-test-case
with classifier,, log.txt,, tiles-log.txt
> In a multi-module projet, I build an aggregated Javadoc for the site.
> The project is built with "mvn clean deploy site-deploy"
> When I add a new project, the next build always fails because the javadoc plugin can't
find at least one snapshot for the new added module
> In the following example, I added a new module tele.persistance:pers-commons, which have
never been built before.
> Maven tries to download it but it can't find it (never build before).
> {noformat} [INFO] [site:site]
> [WARNING] Unable to load parent project from repository: Could not find the model file
> [INFO] Skipped "About" report, file "index.html" already exists for the English version.
> [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
> [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
> [INFO] Generate "JavaDocs" report.
> [INFO] snapshot tele:commons:1.2.0-alpha-1-SNAPSHOT: checking for updates from mirror.snapshots
> [INFO] snapshot tele.persistance:pers-data:1.2.0-alpha-1-SNAPSHOT: checking for updates
from mirror.snapshots
> [INFO] snapshot tele.persistance:pers-api:1.2.0-alpha-1-SNAPSHOT: checking for updates
from mirror.snapshots
> [INFO] snapshot tele.persistance:pers-commons:1.2.0-alpha-1-SNAPSHOT: checking for updates
from mirror.snapshots
> Downloading: http://proxy/maven2-snapshots/repository/tele/persistance/pers-commons/1.2.0-alpha-1-SNAPSHOT/pers-commons-1.2.0-alpha-1-SNAPSHOT.jar
> [WARNING] Unable to get resource 'tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT'
from repository mirror.snapshots (http://proxy/maven2-snapshots/repository)
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command: 
>       mvn install:install-file -DgroupId=tele.persistance -DartifactId=pers-commons \
>           -Dversion=1.2.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>   Path to dependency: 
>   	1) tele.persistance:pers-dao:jar:1.2.0-alpha-1-SNAPSHOT
>   	2) tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT
> ----------
> 1 required artifact is missing.
> for artifact: 
>   tele.persistance:pers-dao:jar:1.2.0-alpha-1-SNAPSHOT
> from the specified remote repositories:
>   central (,
>   mirror.snapshots (http://proxy/maven2-snapshots/repository)
> {noformat}
> If I make an intermediate "install", everything works fine

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message