Actually javadocs in droiddoc format has to be passed as DroidDocPaths
property, not JavaDocPaths property which is to parse HTML in default
javadoc format (I believe this is the default, and consistent, but there
is no assurance that java sdk doesn't change the format).
Atsushi Eno
Jonathan Pryor wrote:
On Oct 11, 2012, at 9:20 AM, Jeremy A. Kolb - ARA/NED <jk...@ara.com> wrote:
So I can see that the javadocpath is being populated put nothing api.xml
doesn't change and I don't get any parameter names or comments.
The current javadoc parser is not "robust;" it's "good enough" to parse
Google's javadoc documentation (for processing android.jar), but there many javadoc formats, not
all of which are supported. For example, the Google Maps javadoc format differs from the
android.jar javadoc format, and the Google Maps javadocs cannot be imported at this time.
I'm sorry for the inconvenience.
- Jon
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
