Wendy Smoak wrote:
Keep in mind, however, that the "official" online website actually comes
from the current source code, so it will diverge from the documentation
for the latest GA release as changes are made.
You may find things online that do not apply to your version of Struts,
which is why you should install the struts-documentation.war locally and
refer to it if you need the exact docs for your version.
I've always found this a bit odd (and it's by no means a Struts-only
thing!) -- wouldn't it make more sense for the online documentation to
correspond to the current release and clearly seperate documentation
covering unreleased features? That way, the web site is a current reference
(as opposed to a 'future reference') which ought to reduce user confusion
("the docs say XXX but it doesn't work with the release I downloaded...")
The trouble is, different projects have different conventions for
publishing the documentation corresponding to particular releases. Struts
includes a struts-documentation.war; some projects have release-specific
sections on the web site; some bundle static HTML in the release download;
etc.)
So, the right place to look for reference documentation on release X of
package Y is... err... well, not obvious for most Y... Sorry, just a pet
peeve of mine ;-)
L.
--
Laurie, Open Source advocate, Java geek and novice blogger:
http://www.holoweb.net/laurie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
