The root problem here is that the code to find the localized man pages
doesn't even exist in the server! Ouch! Prior testing of localized man
pages only tested when the server is down, in which case asadmin does all
the work of finding the man page. The fix it to adapt the man-page-finding
code from asadmin so that it can work in the server.
How bad is its impact? (Severity)
Pretty bad. Localized man pages aren't found at all.
Previous 3.x releases haven't provided localized man pages.
How often does it happen? (Frequency)
Even time in non-English locales.
How much effort is required to fix it? (Cost)
It took me several hours to fix it.
What is the risk of fixing it? (Risk)
Moderate. I've isolated the fix to the server code that finds man pages,
even though the asadmin code that does the same should be refactored to
use common code; that will wait for 3.2. The risk is that the fix might
break finding the default man pages in some case that testing won't detect.
Fortunately, the fix is isolated to the man-page-finding code.
Does a work around for the issue exist? Can the workaround be reasonably employed by the end user?
The workaround is to only ask for man pages when the server is down,
or to supply the wrong server coordinates to asadmin so it thinks the
server is down.
If the issue is not fixed should the issue and its workaround (if applicable) be described in the Release Notes?
How long has the bug existed in the product?
Do regression tests exist for this issue?
Not that I'm aware of.
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
Any tests that involve finding man pages. I think the risk of
destabilization outside the man page area is extremely small.
When will a tested fix be ready for integration?