I recently saw defect #29230 against commons-net.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29230
in which the author notices a broken link within the javadocs.  I looked into 
this further and discovered that almost all of the handcoded links in the 
javadocs for commons-net are broken similarly.

These broken links are almost all of the following form

<a href = "org.apache.commons.net.package..../Class.html">

Of course, these won't work.  

Can someone help me answer these questions?

How did they ever work?  
Is this the result of some global search and replace gone awry?
What is the "right" way to express such links in javadoc?  Relative paths?  is 
there some sort of "root" notation that would correctly resolve intra-project 
javadoc links such as these?  Finally, can maven, which generates these page 
from source help somehow in setting these up?

My goal here is to correct this mess with the minimum amount of work possible 
and with the greatest flexibility against future changes.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to