Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343161

Summary:

type can't be resolved when many files are added to project

Product:

[Eclipse Project] JDT

Reporter:

Missing name <noth>

Component:

Core

Assignee:

Stephan Herrmann <stephan.herrmann>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

Olivier_Thomann, pwebster, stephan.herrmann

Version:

3.7

Target Milestone:

4.13 M1

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
testdata with ~50 packages, the problem occurs in test_roundtrip_303	none
screenshot of the problem	none

Description Missing name

2011-04-18 09:56:49 EDT

Build Identifier: 20110218-0911

If we add a lot of java files (~70) to a project and if these files contain classes which have package visibility, these classes can not be resolved. There are error markers in the java editor, even though the type exists.

Reproducible: Sometimes

Steps to Reproduce:
1. create one java file with two classes (one with package visibility, called A)
2. create another java file which accesses the type A
3. if we add these two files (and a lot of other java files at the same time) to a project the error occurs

Comment 1 Missing name

2011-04-18 10:00:10 EDT

Created attachment 193488 [details]
testdata with ~50 packages, the problem occurs in test_roundtrip_303

if we add all these packages to a project the described problem occurs in test_roundtrip_303. ActionFactory can't be resolved, even though it exists.

Comment 2 Missing name

2011-04-18 10:01:35 EDT

Created attachment 193489 [details]
screenshot of the problem

Comment 3 Olivier Thomann

2011-04-19 12:55:34 EDT

I cannot reproduce. Import the attached files in one shot works perfectly fine.

Comment 4 Olivier Thomann

2011-04-19 12:58:06 EDT

I am using I20110412-2200 (4.1 I-build).

Could you please try to reproduce on a newer build ?

Comment 5 Missing name

2011-05-11 09:32:24 EDT

I think the problem is similar to this problem, which should be easy to reproduce: https://bugs.eclipse.org/bugs/show_bug.cgi?id=345417

Comment 6 Eclipse Genie

2019-06-29 16:40:46 EDT

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 7 Stephan Herrmann

2019-06-29 16:43:37 EDT

Closing as per comment 3.