![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mutter grumble (Sun)
Jun. 7th, 2004 12:43 pmGee, thanks, Sun.
In chasing down a bug (failure to run) in javadoc, I came to the tool change log. It records a fix in the standard doclet for the bug I am seeing. We don't use the standard doclet, so we'll have to make the corresponding fix. They provided a link to a bug in their database, which I clicked (in search of a description of the solution).
This brought me to a login page. I don't have an account with them, but they have a link for free registration. I clicked it; it's a 404. So I searched their web site for user registration, found what appeared to be the relevant page, and signed up.
Armed with this registration, I returned to that bug link. This time it did not return a login challenge; instead, it said "this bug is not available".
Grr.
(In the unlikely event that anyone reading this knows what arcane magic I must work to get javadoc to run on code that contains assertions, please let me know. Currently I am commenting out the assertions, which is not a good long-term solution. We use 1.4.01 by default, but it doesn't work with 1.4.2 either.)
In chasing down a bug (failure to run) in javadoc, I came to the tool change log. It records a fix in the standard doclet for the bug I am seeing. We don't use the standard doclet, so we'll have to make the corresponding fix. They provided a link to a bug in their database, which I clicked (in search of a description of the solution).
This brought me to a login page. I don't have an account with them, but they have a link for free registration. I clicked it; it's a 404. So I searched their web site for user registration, found what appeared to be the relevant page, and signed up.
Armed with this registration, I returned to that bug link. This time it did not return a login challenge; instead, it said "this bug is not available".
Grr.
(In the unlikely event that anyone reading this knows what arcane magic I must work to get javadoc to run on code that contains assertions, please let me know. Currently I am commenting out the assertions, which is not a good long-term solution. We use 1.4.01 by default, but it doesn't work with 1.4.2 either.)