[ 
https://jira.codehaus.org/browse/MJAVADOC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306885#comment-306885
 ] 

Patrick M.J. Roth commented on MJAVADOC-116:
--------------------------------------------

I already tried

<execution>
<phase>verify</phase>
</execution>

but it didn't solve the issue.

As far as I have seen, a component (javadoc plugin?, site plugin? or more 
probably the maven framework itself) checks the dependencies very early in  the 
life cycle, independently of the phase at which the javadoc is executed.

I also tried to build with --fail-never. In that case modules are built, but 
the build itself is reported as failed. The site itself is not generated.

However the following works:
mvn install javadoc:aggregate

This could mean that the javadoc plugin is not involved.
                
> Impossible to aggregate javadoc if snapshot never built
> -------------------------------------------------------
>
>                 Key: MJAVADOC-116
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-116
>             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 use.zip, 
> javadoc-plugin-test-case with classifier use.zip, 
> javadoc-plugin-test-case.zip, log.txt, mymobiliartest.zip, 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 '/continuum-folders/working-directory/116/../pom.xml'.
> [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] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [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 (http://repo1.maven.org/maven2),
>   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: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to