We currently have a twofold problem
with our Javadoc: 1.
We keep a copy of it in CVS in the agentcontroller doc plug-in, which requires
manual updates every time that the Javadoc is regenerated, plus the Javadoc
fails our copyright-checking tool and some doc tools. The current version
that we are shipping was last updated in 2005.
People complain that they can't find the Javadoc.
Solution: We have a solution for TPTP V4.2 that
will not affect the TPTP driver. This solution would require an adjustment
to the build process. The build currently generates the Javadoc, one per
project, and posts the Javadoc files on the web.
The proposal is for the build to additionally package that Javadoc in plug-in
JAR files, one for each Project. By wrapping the Javadoc in a plug-in JAR
the user could download the Javadoc from the web page, install it in their
driver, and browse it in the Eclipse Help Contents. This eliminates the
manual updates in CVS.
A new Javadoc central page would be created for the TPTP web page; this
central page would have pointers to the Javadoc on the web, both those
browsable on-line and the new downloadable plug-in JARs. The Downloads
page, Project web pages, and Documentation page would all point to this
central Javadoc page.
This would be a one-time change.
This affects what's posted on the web only; no changes to the TPTP driver
(other than removing the copy of Javadoc from CVS).
I would check in the plug-in stubs that the build would use to wrap the
Javadoc in (the stubs are currently residing only on my hard drive). There
would be one plug-in stub per Project in the development (not web) CVS.
Hubert would modify the build scripts to wrap the Javadoc in the plug-in
stubs and would also update the downloads page to point to the new Javadoc
has been opened against TPTP.Web for this update. Please let me know if
I can proceed - I am asking all of you for your approval because each Project
needs to approve a plug-in being checked in their project in CVS.
IBM Toronto Lab