Bug 33743

Summary:	[content assist] CodeAssist failure dialog shouldn't open for units outside the classpath
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, markus.kell.r
Version:	2.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	stalebug

Description Philipe Mulet

2003-03-04 07:50:01 EST

Build 20030227

In same setup as bug 31799, using codeassist inside Main.java will open a 
failure dialog telling that the unit doesn't exist !?! This is an internal 
detail of the JavaModel which shouldn't be surfaced to an end-user.

Ringing the bell should be enough

Comment 1 Philipe Mulet

2003-03-05 06:09:06 EST

Along the same line, on following unit (in non-Java project):

class A {
	void f<CODEASSIST HERE>


The failure dialog opens, and when closing it, template completions are 
proposed !?! It should consistently fail as well (the entire codeassist should 
be turned off as soon as a unit isn't on the classpath).

Comment 2 Markus Keller

2007-12-11 07:00:47 EST

In I20071211-0010, I even get the "cu is not on the classpath" dialog twice. And if I don't click OK quickly enough, I get the content assist timeout dialog.

Comment 3 Eclipse Genie

2019-12-15 13:17:12 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Dani Megert

2019-12-17 05:15:41 EST

Still an issue if it is not a Java project.

Comment 5 Eclipse Genie

2021-12-08 15:56:39 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Eclipse Genie

2023-11-29 12:39:40 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.