The trick is this option in build.xml:
    <invoke-module-javadoc linksource="yes">

After that you can refer to source code of all classes via src-html folder. 
Unfortunately, this creates source file html for all java classes, not only 
referenced ones. For demo this was not a problem, as there are only 3 .java 
files. This option also makes all method declarations in javadocs "hot" 
pointing to the source code line. Again very nice for demo code...

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]


> -----Original Message-----
> From: Robert Muir [mailto:[email protected]]
> Sent: Monday, September 10, 2012 6:37 PM
> To: [email protected]
> Subject: Re: svn commit: r1382633 -
> /lucene/dev/trunk/lucene/spatial/src/java/overview.html
> 
> On Mon, Sep 10, 2012 at 12:23 PM, Smiley, David W. <[email protected]>
> wrote:
> > I figured that is why the decision was made.  I think exceptions can be made
> as long as one understands the down side.  An alternative solution to this
> decision is to simply make sure the URL doesn't 404.
> >
> 
> The issue in general is that the docs are 'versioned' so it could be ok now, 
> and
> we could release 4.0, and then the 4.0 docs are later broken by API changes,
> code movements, etc.
> 
> Separately there was a recent thread about examples (Dawid Weiss responded
> with some ideas they used in carrotsearch): I still feel we need to do some 
> work
> here.
> 
> The demo module links in its 'examples' into the javadocs with a javadoc 
> option
> (http://lucene.apache.org/core/4_0_0-BETA/demo/overview-
> summary.html#Location_of_the_source),
> so thats one way to do it. Dawid had a different idea that would also work I
> think.
> 
> --
> lucidworks.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to