Arthur,
I agree with the need to keep the javadoc at a stable
location. I personally like the ".../webtools/<subproject/api/index.html"
location since it's short and easy to remember. Perhaps our build process should
just automatically update that location with the latest version?
The J2EE Tools team will go ahead and update our javadoc
with @since -- perhaps Tim could do the same for Server Tools?
Another piece that I'd like to propose is that all API
package summaries include a UML diagram of the exposed API (as in modulecore) to
give our consumers a quick overview of what's available. Those internal to IBM
should able to do this quickly with RSA and perhaps we could find another
opensource UML2 editor for non-IBMer-types. Any thoughts?
-------------------------------------------------------------------------
Kind Regards,
Michael D. Elder
Rational Studio / J2EE Tools
Development
IBM RTP Lab
Ext: (919) 543-8356
T/L: 441-8356
mdelder@xxxxxxxxxx
Friday, February 18, 2005 6:07 PM
To: wtp-dev@xxxxxxxxxxx
cc:
wtp-dev@xxxxxxxxxxx, wtp-dev-admin@xxxxxxxxxxx
From: Arthur Ryman
<ryman@xxxxxxxxxx>
Subject: Re: [wtp-dev] API Documentation publish
process