Re: Javadoc Linking - !!Baffling!!

[Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>]

* dion@multitask.com.au <di...@multitask.com.au> [2003-12-02 08:10]:

> Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> wrote on 30/11/2003 
> 06:42:35 PM:
> 
> > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-11-28 
> 23:55]:
> > > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-11-27 
> 21:41]:
> > > > Dion?
> > > > 
> > > > I've fixed the problem I was having with Javadoc linking. I create a
> > > > temporary directory and copy the source fields specified by the
> > > > includes and excludes. I then run Javadoc on that directory. It
> > > > works well.
> > > > 
> > > > Interested? I can JIRA and patch.
> > > 
> > > Still wondering...
> > 
> > A patch is attached...

> Surely there's a better way than copying the source.....

I just pulled and build maven from cvs. Unlike the Javadoc at
http://maven.apache.org/apidocs/index.html, my local build of Maven
DID NOT generate cross-reference links to classes within the same
package under the package heirarchy of org.apache.maven.*

I've fixed this locally, by copying the Javadoc source files to a
temporary directory based on the includes and excludes. It seems
that the Javadoc Ant task will not generate cross-references when
source files are specified using a file set.

Of course, I could specify a link to the project Javadoc, but that
requires an absolute path and does not generate Javadoc suitable for
redistribution.

I've read the build.properties file that comes with Maven, I've
built Maven locally, I can't see why the Maven site has
cross-reference links and my checkout build doesn't.

Anyone? Anything?

-- 
Alain Javier Guarnieri del Gesu - javi@ajgdg.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org