Community
Participate
Working Groups
we should probably set a milestone for when we would expect javadoc to appear on the API classes. I realize the problems with doing it too soon, but if we decide on a milestone we'll have a little lead time to deal with it.
Agreed. M3?
M4 because things may change significantly as we move toward more advanced scenarios.
I've been filling in javadoc as I make changes in various places, but a comprehensive API cleanup won't happen until 3.5. We may also have some time very late in the 3.4 cycle since doc only changes are low risk.
API is no longer considered for 3.5.
The file /org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt contains a link to <http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc>, which explains how to add docs, especially: "platformOptions.txt: - code of required plug-ins must be added on the -classpath (the JAR(s)for non-JARed plug-ins and <plugin>/@dot for JARed plug-ins". In M5, the classpath contained duplicates of plug-ins that have been added to the sourcepath, but did not contain all dependencies of the added plug-ins. I've fixed that for I20100202-0800.
Marking fixed.