Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364881 - JavaDoc not shown in ExtDoc & Tooltip
Summary: JavaDoc not shown in ExtDoc & Tooltip
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Recommenders (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Marcel Bruch CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-26 02:47 EST by Michael Woski CLA
Modified: 2019-07-24 14:35 EDT (History)
2 users (show)

See Also:


Attachments
just a snapshot (44.86 KB, image/png)
2011-11-26 02:48 EST, Michael Woski CLA
no flags Details
Completion on "Activator extends AbstractUIPlugin" (30.35 KB, image/png)
2012-02-07 07:09 EST, Marcel Bruch CLA
no flags Details
Example Preference Settings (180.32 KB, image/png)
2012-02-07 07:09 EST, Marcel Bruch CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Woski CLA 2011-11-26 02:47:20 EST
As the title says, the javadoc information is not shown in neither the ExtDoc view nor in the hoovers. The normal Javadoc view however, does show the information.
I'm running a recent 0.4.0 recommenders on top of a Juno milestone build.
The extdoc.providers package is properly resolved/started.
Comment 1 Michael Woski CLA 2011-11-26 02:48:46 EST
Created attachment 207563 [details]
just a snapshot
Comment 2 Marcel Bruch CLA 2011-11-26 04:32:12 EST
Thanks for reporting Michael.

Stefan, any ideas what may cause this/where to look at to figure out whats going wrong?
Comment 3 Stefan Henss CLA 2011-12-01 01:28:06 EST
Hi Michael,

as you seem to experience those issues on Linux, I believe they are related to another bug with Javadoc and Linux: https://bugs.eclipse.org/bugs/show_bug.cgi?id=364079

Can you verify this?

Thanks
Comment 4 Michael Woski CLA 2011-12-01 04:12:30 EST
(In reply to comment #3)
> Hi Michael,
> 
> as you seem to experience those issues on Linux, I believe they are related to
> another bug with Javadoc and Linux:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=364079
> 
> Can you verify this?
> 
> Thanks

I don't get to that point where I could even observe such a behaviour :-(
Comment 5 Marcel Bruch CLA 2012-02-02 01:24:55 EST
Michael,

again, thanks for reporting. I think this issue should be fixed in the latest version. Do you mind testing the latest dev build to see whether this is properly fixed in 0.5?

Update site urls have changed:

http://download.eclipse.org/recommenders/updates/dev/e42/
http://download.eclipse.org/recommenders/updates/dev/e37/

Due to several namespace refactorings for Juno, 0.4 has to be uninstalled before installing 0.5.
Comment 6 Michael Woski CLA 2012-02-07 05:07:35 EST
(In reply to comment #5)
> Michael,
> 
> again, thanks for reporting. I think this issue should be fixed in the latest
> version. Do you mind testing the latest dev build to see whether this is
> properly fixed in 0.5?
> 
> Update site urls have changed:
> 
> http://download.eclipse.org/recommenders/updates/dev/e42/
> http://download.eclipse.org/recommenders/updates/dev/e37/
> 
> Due to several namespace refactorings for Juno, 0.4 has to be uninstalled
> before installing 0.5.

well, 2 things ... first, the ExtDoc view shows the JavaDocs indeed - mission accomplished I'd say.
Second though, and that's the bad message, I still don't get any content assists from recommenders.

bye Mich;
Comment 7 Marcel Bruch CLA 2012-02-07 05:15:36 EST
Thanks for testing! That's good and bad news at the same tim :-\ 

Two fast follow-ups:

1. On which types did you test?
ATM only Eclipse APIs are supported (JFace, SWT, UI etc.). For M6 support for java.* is planned.

2. Which server url do you use?
"Preferences » Code Recommender » Extdoc » Webservice URL:" should point to http://213.133.100.41/extdoc/

(click on "Reset" may help)
Comment 8 Michael Woski CLA 2012-02-07 06:41:02 EST
(In reply to comment #7)
> Thanks for testing! That's good and bad news at the same tim :-\ 
> 
> Two fast follow-ups:
> 
> 1. On which types did you test?
> ATM only Eclipse APIs are supported (JFace, SWT, UI etc.). For M6 support for
> java.* is planned.

I tried with org.eclipse.ui.plugin.AbstractUIPlugin and using "this." did not show anything when only recommender assists were enabled

> 
> 2. Which server url do you use?
> "Preferences » Code Recommender » Extdoc » Webservice URL:" should point to
> http://213.133.100.41/extdoc/

I had this url

> 
> (click on "Reset" may help)
Comment 9 Marcel Bruch CLA 2012-02-07 07:09:09 EST
Created attachment 210639 [details]
Completion on "Activator extends AbstractUIPlugin"

this should work. I've tested with:


public class Activator extends AbstractUIPlugin {

    public static final String PLUGIN_ID = "org.eclipse.recommenders.examples.demo"; //$NON-NLS-1$

    private static Activator plugin;

    public static Activator getDefault() {
        return plugin;
    }

    @Override
    public void start(final BundleContext context) throws Exception {
        // super.start(context);
        plugin = this;
        super.<^SPACE>
    }

    @Override
    public void stop(final BundleContext context) throws Exception {
        plugin = null;
        this.<^SPACE>
        
        // super.stop(context);
    }
}

Does extdoc view show anything when you select "AbstractUIPlugin" in type declaration?

How does your model store look like? Is there anything 'dark-orange' in "Preferences » Code Recommenders » Calls" as shown in the attached screenshot?

Thanks for you help to hunt down this issue.
Comment 10 Marcel Bruch CLA 2012-02-07 07:09:40 EST
Created attachment 210640 [details]
Example Preference Settings
Comment 11 Michael Woski CLA 2012-02-07 07:46:27 EST
(In reply to comment #9)

> Does extdoc view show anything when you select "AbstractUIPlugin" in type
> declaration?

Yeah, that is what actually is working. ...

> 
> How does your model store look like? Is there anything 'dark-orange' in
> "Preferences » Code Recommenders » Calls" as shown in the attached screenshot?

... and that is also looking fine here.

> 
> Thanks for you help to hunt down this issue.

are there any suspicous code fragments that I could try and put some breakpoints in?
Comment 12 Marcel Bruch CLA 2012-02-07 07:59:10 EST
(In reply to comment #11)
> are there any suspicous code fragments that I could try and put some
> breakpoints in?


org.eclipse.recommenders.internal.completion.rcp.calls.engine.CallsCompletionProposalComputer.computeCompletionProposals(ContentAssistInvocationContext, IProgressMonitor)

is the method where the completions are computed. It would be great to know where (in which step) exactly the computer stops and then figuring out why. The top-level steps should be quite simple to understand.

I assume that the models should be there. A wild guess is that the query computation is doing bad things. If you could post the query (computed in completeQuery()) and send your example source file / project would be great.

If you need further examples, I can share lots of examples in another git repository.
Comment 13 Marcel Bruch CLA 2012-06-09 15:49:01 EDT
I can't reproduce and it works in current RC1 milestone builds for me. please reopen if the problem persists.