Bug 534906 - [model] JavaModelException thrown when processing a non-java project
Summary: [model] JavaModelException thrown when processing a non-java project
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2018-05-21 04:28 EDT by Manoj N Palat CLA
Modified: 2023-08-15 17:49 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manoj N Palat CLA 2018-05-21 04:28:43 EDT
Follow-up of bug 486979 comment 15
See bug 486979 comment 7 for reproducible steps 
(reproduced below)

Created attachment 274078 [details] 
Repro project

Import the attached project - it's a general project, no Java nature.
Open Bug486979.java - it's a blank file
Open Type Hierarchy on java.util.Map.
Show subtypes - oops none.

If you set a breakpoint on JavaModelException, it is clear that an open *.java file in a non-Java project is being disruptive. Bad projects should be ignored.

See also bug 486979 comment 8, 12, 14.
Comment 1 Sarika Sinha CLA 2018-08-17 06:16:24 EDT
I was able to reproduce it in June but now with latest version of I build I am not able to reproduce this problem. 
That is I and Manoj can see the subtypes even with the blank java file open in a non java project.
Comment 2 Ed Willink CLA 2018-08-17 06:25:29 EDT
If you recall, you provided a local fix to a generic problem, so it is not surprising that the original repro is cured. The challenge is to handle all the similar use cases.
Comment 3 Manoj N Palat CLA 2019-02-11 04:27:44 EST
Bulk move out of 4.11
Comment 4 Sarika Sinha CLA 2019-05-22 05:37:21 EDT
Resolving it as Works For Me, Please reopen if you have a specific scenario to reproduce.
Comment 5 Ed Willink CLA 2019-05-22 06:08:13 EDT
I don't understand. 

Bug 486979 identified a real problem. Due to time scales, it was resolved by a local fix hiding the underlying problem..

Bug 486979#c15 directed to open this bug to investigate the general problem of ignoring rather than throwing JME for bad projects.

I see no report on a review of all such JME throwing so surely this bug remains open pending that review?
Comment 6 Sarika Sinha CLA 2019-05-22 06:41:30 EDT
Reopening it, as we will be good to have some analysis done.
Comment 7 Sarika Sinha CLA 2019-05-22 06:42:20 EDT
(In reply to Sarika Sinha from comment #6)
> Reopening it, as we will be good to have some analysis done.

we* > it
Comment 8 Eclipse Genie CLA 2021-08-21 12:42:11 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 9 Eclipse Genie CLA 2023-08-15 17:49:22 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.