Just a quick update: The major blocker I'm dealing with now is that
Maven considers javadoc complaints to be ERRORs, and we have a lot of
javadoc that does not conform to current usage -- use of non-HTML tags
in the text without escaping the <> delimiters, badly formed HTML,
missing *param or *throws lines.
I've changed a lot, and there are still at least 200 errors to remove
(though some of them are multiple complaints about a single line of
documentation).
As previously noted, I *could* put all the files through Maven's
automatic javadoc:fix process. But I think that would result in more
changes than I'm applying, and in less meaningful changes in many cases,
so I'm still wading through this by hand. We can consider running a
separate javadoc:fix after we're on Maven.
As previously noted, the *RIGHT* answer for a lot of this is to take
advantage of Javadoc inheritance rather than explicitly writing javadoc
for everything, augmented by the /** ${@inheritDoc} **/ mechanisms if we
need to add comments to the inherited documentation to explain what this
implementation does differently. But, again, that's much more change and
really isn't a priority. I may open a Jira item for this, low priority
but perhaps a good place to use a volunteer who doesn't know the code yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
