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

Reply via email to