Bug 7797 - Add support for javadoc 1.7.0_04 output for .jar bindings
Summary: Add support for javadoc 1.7.0_04 output for .jar bindings
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.2.x
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-10-11 10:01 UTC by Jeremy Kolb
Modified: 2013-08-23 14:35 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Project (1.11 MB, application/zip)
2012-10-11 11:14 UTC, Jeremy Kolb
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
VERIFIED FIXED

Description Jeremy Kolb 2012-10-11 10:01:26 UTC
I have generated Javadocs for the jars used in http://docs.xamarin.com/android/tutorials/Binding_a_Java_Library_%28.jar%29 but they don't see to be getting picked up during the build: method names and comments are not being pulled into the generated assemblies.

See the attached zip file.
Comment 1 Jeremy Kolb 2012-10-11 11:14:14 UTC
Created attachment 2735 [details]
Project

Oops, it looks like I forgot to attach the project.
Comment 2 Atsushi Eno 2012-10-13 10:19:34 UTC
The "javadoc" is not in the standard Javadoc format that we support. You need to generate javadoc output with standard old-fashion doc template.
Comment 3 Jonathan Pryor 2012-10-13 14:42:44 UTC
This is actually a request to add support for parsing JavaDoc 1.7.0_04 output. There are likely a number of javadoc formats that we don't currently support, and we will need to add support for them.
Comment 4 Steve Williams 2013-01-06 22:03:25 UTC
If javadocs could be treated the same as other attributes (generated code could use them direct from the jar or we can transform them via Metadata.xml), that would be perfect.  Once we start transforming attributes, the javadocs won't match so we would have to transform them as well.
Comment 5 Atsushi Eno 2013-01-07 01:38:43 UTC
jars don't contain parameter names.
Comment 6 Atsushi Eno 2013-07-19 02:22:30 UTC
This is now implemented. Not likely in the next major release; next to next. [master dbad0c0]
Comment 7 Steve Williams 2013-07-19 02:25:21 UTC
Thanks Atsushi.
Comment 8 Akhilesh kumar 2013-08-23 14:35:01 UTC
We have checked this issue with the following builds:

All Mac
XS 4.1.9 (build 6)
Mono 3.2.2 ((no/a0fc6ba)
MFA 4.8.02054


First we have opened Metadata.xml file and Inside OsmDroid/Transforms added a line to line 31:
 <remove-node path="/api/package[@name='org.osmdroid.views.overlay']/class[@name='OverlayManager']" />

we able to build an application successfully.Then in obj/Debug/OsmDroid.dll
we are able to see all classes and methods in assembly info.

Hence marking this issue as a verified fixed.