On Apr 6, 2009, at 4:26 PM, Mike Schrag wrote:
people to extend the javadoc. I considered also making it so a
doclet would pull that content into the real javadoc at build
time, but Chuck mentioned that Sun provide doclets in 1.5? I'm
still not convinced I believe him, though :)
Well, when I said that I used real English sentences. ;-) And
what I said was that Sun is changing the API and so made it private
in 1.5 thus preventing any custom doclets being generated.
Wow. When I typed that my brain said "broke" ... fingers typed
"provide" In my defense I had a 3 yr old saying
"daddy.daddy.daddy.daddy." while typing it. It's sort of amazing I
didn't type "murder" instead.
ROFL. Yeah, I can see that.
"Sun implemented a lock-out in the doclet toolkit API to prevent
others from using it The idea was to develop the toolkit further to
finalize it and then remove the lock and make the API public. It's
unknown when or if Sun would remove this lock. Both the Standard
and MIF doclets use the doclet toolkit."
Wonder has those @binding things that show up in javadoc -- how do
those work?
Those be taglets. Taglets work, but they are very restrictive in what
they can do. Doclets are much more flexible. Well, other than in you
can't easily do so in JDK 1.5
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
