You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2009/09/11 10:46:31 UTC
[jira] Closed: (MJAVADOC-260) Javadoc report not generated for
multi-module project if run from parent level - error resolving
dependencies
[ http://jira.codehaus.org/browse/MJAVADOC-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MJAVADOC-260.
------------------------------------
Resolution: Duplicate
It is a Maven issue and not a Javadoc plugin issue, see MNG-3685
> Javadoc report not generated for multi-module project if run from parent level - error resolving dependencies
> -------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-260
> URL: http://jira.codehaus.org/browse/MJAVADOC-260
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: Windows XP, JDK 1.6.0_12
> Reporter: Tom Forwood
> Attachments: tstmvn.zip
>
>
> Similar perhaps to bug http://jira.codehaus.org/browse/MJAVADOC-181 reported as fixed in version 2.6
> Javadoc plugin fails to correctly compute dependencies between modules
> attached project structure will generate error when mvn site:site is run
> ...
> [INFO] Building subproject2
> [INFO] ------------------------------------------------------------------------
> [INFO] No goals needed for project - skipping
> [INFO] Preparing javadoc:javadoc
> [INFO] No goals needed for project - skipping
> [INFO] Preparing javadoc:test-aggregate
> [INFO] ------------------------------------------------------------------------
> [INFO] Building tstmvn
> [INFO] ------------------------------------------------------------------------
> [INFO] No goals needed for project - skipping
> [INFO] ------------------------------------------------------------------------
> [INFO] Building subproject1
> [INFO] ------------------------------------------------------------------------
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] No sources to compile
> [INFO] ------------------------------------------------------------------------
> [INFO] Building subproject2
> [INFO] ------------------------------------------------------------------------
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] snapshot tst.tstmvn:subproject1:0.0-SNAPSHOT: checking for updates from digital-sales-maven2
> Downloading: http://digital-sales-tech/maven2/tst/tstmvn/subproject1/0.0-SNAPSHOT/subproject1-0.0-SNAPSHOT.jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) tst.tstmvn:subproject1:jar:0.0-SNAPSHOT
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=tst.tstmvn -DartifactId=subproject1 -Dversion=0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=tst.tstmvn -DartifactId=subproject1 -Dversion=0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) tst.tstmvn:subproject2:jar:0.0-SNAPSHOT
> 2) tst.tstmvn:subproject1:jar:0.0-SNAPSHOT
> ----------
> 1 required artifact is missing.
> for artifact:
> tst.tstmvn:subproject2:jar:0.0-SNAPSHOT
> from the specified remote repositories:
> digital-sales-maven2 (http://digital-sales-tech/maven2),
> central (http://repo1.maven.org/maven2)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira