[
http://jira.codehaus.org/browse/MOJO-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251142#action_251142
]
Anders Hammar commented on MOJO-1618:
-------------------------------------
>From mail conversation on the dev list:
I agree that "current" can't be right.
The problem is that every plugin should be responsible to refer to the right
version.
Maybe the closest we can get is by ${project.prerequisite.maven} and set it by
default to 2.0 to give it at least a value.
Although there are no apidocs for this version this looks to me the best
solution: it's not worse than the current situation and good configured
mojo-projects will link to the right version.
This is pure theory, haven't tried it. My guess is that this should work.
-Robert
Date: Wed, 5 Jan 2011 10:58:37 +0100
From: [email protected]
To: [email protected]
Subject: [mojo-dev] Redirect errors for some old Maven API docs urls when
creating mojo site javadoc
- Hide quoted text -
For the site JavaDoc generation, the mojo-parent 27 declares some links to
maven API docs:
<link>http://maven.apache.org/ref/current/maven-artifact/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-artifact-manager/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-model/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-plugin-api/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-project/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-reporting/maven-reporting-api/apidocs/</link>
<link>http://maven.apache.org/ref/current/maven-settings/apidocs/</link>
These are redirected to urls where 'current' is replaced by the currently
latest Maven version ('3.0.1' currently). However, some of these projects don't
exist in Maven 3.0.x and the redirects end up on a not found page.
The urls having this problem are:
http://maven.apache.org/ref/current/maven-artifact-manager/apidocs/
http://maven.apache.org/ref/current/maven-project/apidocs/
http://maven.apache.org/ref/current/maven-reporting/maven-reporting-api/apidocs/
It's not a major issue, but we don't get nice hyper links in the site javadocs
we're building since Maven 3.0 was released. An easy fix would be to hard-code
'2.2.1' instead of 'current' for those projects that have been removed in
3.0.x. But a possibly more correct solution would be to replace these urls with
the new ones introduced in Maven 3.0.x. WDYT?
/Anders
> 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
>
> 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
