Probably my fault back when we changed package names. Sorry about that.
On Sun, 27 Jun 2004 23:51:45 -0400, Daniel F. Savarese [EMAIL PROTECTED]
said:
In message [EMAIL PROTECTED], Steve Cohen
writes:
These broken links are almost all of the following form
a href =
In message [EMAIL PROTECTED], Jeffrey D. Brekke writes:
Probably my fault back when we changed package names. Sorry about that.
I don't think it occurred to anyone at the time that there were
all of those hardcoded links that needed to be converted. If it's
anyone's fault, it's mine since I
In any case, thank you Daniel.
On Tuesday 29 June 2004 7:39 pm, Daniel F. Savarese wrote:
In message [EMAIL PROTECTED], Jeffrey D. Brekke writes:
Probably my fault back when we changed package names. Sorry about that.
I don't think it occurred to anyone at the time that there were
all of
I just pushed the site out. While I did not want to do another release (had I
known Daniel could fix it so quickly I would have waited), I thought that at
least the docs on our site should get the fixes, so I pushed the site and
they do now, indeed, work.
On Tuesday 29 June 2004 7:39 pm,
Have at it, Daniel. You can surely do the job quicker than I can.
On Sunday 27 June 2004 10:51 pm, Daniel F. Savarese wrote:
In message [EMAIL PROTECTED], Steve Cohen writes:
These broken links are almost all of the following form
a href = org.apache.commons.net.package/Class.html
Of
In message [EMAIL PROTECTED], Steve Cohen writes:
Have at it, Daniel. You can surely do the job quicker than I can.
Alrighty, I'll get to it and report back when I finish.
daniel
-
To unsubscribe, e-mail: [EMAIL
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
Steve Cohen wrote:
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?
In message [EMAIL PROTECTED], Steve Cohen writes:
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
