[
http://jira.codehaus.org/browse/MOJO-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1618.
--------------------------------
Resolution: Fixed
Fixed in [rev. 13417| http://fisheye.codehaus.org/changelog/mojo/?cs=13417]
Introduced a new property in the parent: {{mojo.javadoc.mavenVersion}}, which
is by default set to $\{project.prerequisites.maven\} (which again is by
default 2.0).
Now you will have full control over the version to use.
> Invalid links used for m-javadoc-p
> ----------------------------------
>
> Key: MOJO-1618
> URL: http://jira.codehaus.org/browse/MOJO-1618
> Project: Mojo
> Issue Type: Bug
> Components: _Mojo Parent
> Environment: mojo-parent:27
> Reporter: Anders Hammar
> Assignee: Robert Scholte
>
> The mojo-parent lists several links in the configuration for m-javadoc-p.
> Some of them are for Maven artifacts, which are redirected to the javadoc of
> the current Maven version. Since Maven 3.0 refactored Maven, some of these
> don't work any more:
> Here's the three links complained about:
> [INFO] Generating "JavaDocs" report.
> [ERROR] Error fetching link:
> http://maven.apache.org/ref/current/maven-artifact-manager/apidocs/package-list.
> Ignored it.
> [ERROR] Error fetching link:
> http://maven.apache.org/ref/current/maven-project/apidocs/package-list.
> Ignored it.
> [ERROR] Error fetching link:
> http://maven.apache.org/ref/current/maven-reporting/maven-reporting-api/apidocs/package-list.
> Ignored it.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
