Comment 1 Olivier Thomann 2003-08-12 09:29:29 EDT

Move to JDT/UI.

Comment 2 Dani Megert 2003-08-15 08:58:19 EDT

I assume you want this for the information that's shown in the hovers?

Valid feature - not all companies provide source along with their produc code.

Comment 3 Dani Megert 2003-08-18 10:44:15 EDT

*** Bug 41640 has been marked as a duplicate of this bug. ***

Comment 4 Dani Megert 2003-08-27 06:48:00 EDT

*** Bug 21474 has been marked as a duplicate of this bug. ***

Comment 5 Dani Megert 2004-05-28 07:01:46 EDT

*** Bug 64096 has been marked as a duplicate of this bug. ***

Comment 6 Dani Megert 2004-06-03 08:37:19 EDT

*** Bug 65310 has been marked as a duplicate of this bug. ***

Comment 7 Ed Burnette 2005-01-12 08:54:09 EST

I think it should be 'in addition to' and not 'instead of'. I.e., if the source
is not available, go to the javadoc.

Comment 8 Steve Bang 2005-02-14 14:19:22 EST

Access to Javadoc comments in the context of coding within Eclipse improves 
the productivity of developers, without requiring them to stop and look up 
Javadoc information manually.  Since commercial source code is usually not 
available, fixing this bug would provide an immediate benefit to most Eclipse 
users. Can someone take another look at this issue and see if a fix can be 
provided ASAP? 

Steve

Comment 9 Steve Bang 2005-02-14 19:35:47 EST

I just tested IntelliJ 4.5 and the functionality requested here works great in
IntelliJ. Javadoc comments appears in hover help, reading in from the HTML
Javadoc documentation and it does NOT require source to be available.

Steve

Comment 10 Zohar Amir 2005-03-10 01:44:29 EST

This information should also be used for naming overided/implemented methods
that are created by eclipse (instead of arg0, arg1, etc...).

Comment 11 arne anka 2005-04-06 05:38:41 EDT

this issue is nearly 2 years old and still unfixed! i don't think it's "enhancement" but at least "major". 
parsing javadocs by "classname.html#method" should be much easier the parsing sources, i think.

Comment 12 Steve Bang 2005-04-22 17:41:32 EDT

If the Javadoc information is parsed from the HTML Javadoc files instead of
source files, it will be possible for products to support translated Javadoc
files.  Thus, the source Javadoc comments can be in English, while a user could
access translated Javadoc comments in their own language, if available.  So,
either the Javadoc comments should always be displayed based on the HTML Javadoc
files, or there needs to be a mechanism (preference option) so that a user can
specify that even if the source code Javadoc comments are available, the
specified HTML files (translated) will be used instead. 

Comment 13 Jens Elkner 2005-04-23 03:50:54 EDT

Seems, that still nobody listens. Since it is a major drawback wrt. other IDEs
and is becoming more and more a knock-out criteria (+ always switching between
eclipse and the external browser is more than annoying) severity should be major
and perhaps than someone starts to work on it (parsing javadoc generated files
isn't a big thing ...).

Comment 14 Dani Megert 2005-04-24 10:35:31 EDT

>(parsing javadoc generated files isn't a big thing ...).
We will be happily accept high quality patches.

Comment 15 Tom Hofmann 2005-06-03 02:29:09 EDT

*** Bug 98154 has been marked as a duplicate of this bug. ***

Comment 16 Frederic Plante 2005-06-17 10:45:52 EDT

The fact existing commiters are not working on this defect can certainly be 
attributed to this defect's P3 assigned priority. From the comments above and 
the number of votes, it seems the priority of this defect needs to be 
reevaluated.

Comment 17 John 2005-07-21 13:50:40 EDT

This would be *REALLY* helpful. I think it should be high priority.

--John

Comment 18 David Rabinowitz 2005-07-25 05:25:49 EDT

This is one of the features I'm most looking for. The source is not always
available, but there Javadoc is.

Comment 19 Dani Megert 2005-08-24 05:58:37 EDT

*** Bug 107565 has been marked as a duplicate of this bug. ***

Comment 20 Olivier Thomann 2005-10-20 13:48:03 EDT

I'll take over ownership of this bug in order to provide an API for the UI to
work with. See bug 110173.

Comment 21 Dani Megert 2005-11-10 10:23:27 EST

I guess the rest is our work. Feel free to reassign to text inbox.

Comment 22 Olivier Thomann 2005-11-10 10:27:48 EST

Move to JDT/Text inbox.

Comment 23 Dani Megert 2005-12-05 12:30:11 EST

Fixed in HEAD.
Available in builds >= N20051206-0010.

Comment 24 Tom Hofmann 2005-12-13 05:42:52 EST

verifying...

Comment 25 Tom Hofmann 2005-12-13 06:44:28 EST

verified works on I20051213-0010. Also verified that parameter names are extracted and that this feature does not block content assist.

Comment 26 Olivier Thomann 2006-04-21 13:36:29 EDT

*** Bug 77475 has been marked as a duplicate of this bug. ***

Comment 27 Peter Davie 2006-04-27 12:04:49 EDT

Hi,
I've just downloaded 3.1.2 and this major irritating bug still occurs. Did the fix noted below make it into this release?
Thanks,
Peter

Comment 28 Ismael Juma 2006-04-27 12:11:13 EDT

(In reply to comment #27)
> I've just downloaded 3.1.2 and this major irritating bug still occurs. Did the
> fix noted below make it into this release?

Given that the Target Milestone is "3.2 M4", it's only logical that you still have the problem in 3.1.2. You need to download a 3.2 build to be able to enjoy this feature.

Comment 29 Peter Davie 2006-04-27 12:21:27 EDT

Oops! Missed that. Thanks.