Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    I don't think it's just a case of renaming -- see download.oracle.com/javase/1.5.0/docs/tooldocs/windows/… Commented Jan 28, 2011 at 15:36
  • Quite true. It should be easy to grab the content from inside the html body tag, put that in indented form into a javadoc comment, and append the FQN for the package. I'll put it down as a project to do over the next week. Commented Jan 28, 2011 at 15:58
  • This is a good start, tnx :) Just wondering if it covers all corner cases, like {@link ...} {@value } and whatnot. Also, how do xml escape characters come into this? Also, we'll probably do trim() around the <body> stuff, as well fail-fast if it doesn't find <body>. And sometimes <html> and <body> are on the same line. Commented Jan 28, 2011 at 18:11
  • 1
    What corner cases? It doesn't perform any conversion whatsoever. And you are correct that it doesn't perform the parsing properly, but I doubt that the javadoc tool did full HTML parsing on package.html. Commented Jan 28, 2011 at 18:20