Bug 527322 - [9] Error Reported on Code Editor when the module dependency is added as an internal jar file
Summary: [9] Error Reported on Code Editor when the module dependency is added as an i...
Status: NEW
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:
Depends on:
Blocks:
 
Reported: 2017-11-16 01:27 EST by Kalyan Prasad Tatavarthi CLA
Modified: 2022-07-18 19:57 EDT (History)
0 users

See Also:

Attachments
test Modules (5.58 KB, application/x-zip-compressed)
2017-11-16 01:27 EST, Kalyan Prasad Tatavarthi CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kalyan Prasad Tatavarthi CLA 2017-11-16 01:27:15 EST 
Created attachment 271491 [details]
test Modules

Import the projects attached in the attachment and open the file One.java in project test1, there will be an error reported on line numbers 3 and 8 
as 1) The import testTwo cannot be resolved 
   2) Two cannot be resolved

but the problems view does not report any error and we can successfully run the project as a java application.

Now Go to the Properties > Java Build path > Libraries and remove the jar testTo.jar from modulePath and add it as an external jar file.

Now these two error are gone from the file One.java
Comment 1 Eclipse Genie CLA 2020-07-05 15:48:48 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 2 Eclipse Genie CLA 2022-07-18 19:57:13 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.