On 01/02/2012 07:21 AM, David Karr wrote:
This may be completely Eclipse-specific, but perhaps not.
I find it's very inconsistent whether I can get Eclipse to show me the
Javadoc for an Android class or method, even when I appear to have valid
javadoc attached to the "android.jar" file.
For instance, right now I'm viewing a class in a sample application that
references SQLiteDatabase. There are no compile errors, so I have all of
my dependencies properly set. I hover on the class name reference and
force the javadoc to display, it prints the class name as
"android.database.sqlite.SQLiteDatabase", but it says "Note: This
element has no attached source and the Javadoc could not be found in the
attached Javadoc.".
I then went into the Project Explorer and expanded the "Android 2.3.3"
library, exposing the "android.jar" file. I right-clicked on that and
selected Properties. I clicked on "Javadoc Location". It's currently set
to "Javadoc URL" and the "Javadoc location path" was set to the path to
the "reference" directory in the android SDK. I clicked "Validate" and
it said "Location is likely valid".
Just in case, I verified that
"android/database/sqlite/SQLiteDatabase.html" exists at the root of the
javadoc tree.
So why is it not showing the javadoc for this class?
Hi,
I faced the exact same issue...
it comes down to the fact that Eclipse assume the sources will be always
more reliable of the javadoc.
Actually I would think the opposite since the source may contain
auto-generated content or, like in the android case, be integrated with
additional metadata (the SDK version a function has been introduced).
Shame Eclipse for that.
I discussed a lot in the #eclipse channel on freenode (IRC).. They
insist Google is doing something out of specification by adding data to
the javadoc (that's the attitude they have).
I opened this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=366811
It has been closed after a short while by setting it duplicate of this one:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=178071
it's opened since 2007 (sic!) and it's currently marked as "helpwanted"
I remember opening the same issue to android bug tracker but can't find
it anymore :/
If you happen to have some news or workaround I'll be happy to know
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
