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

Bug 532162

Summary: non-existing classpath variable causes inconsistent and confusing error marking
Product: [Eclipse Project] JDT Reporter: arne anka <eclipse-bugs>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.8   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
show all three places none

Description arne anka CLA 2018-03-08 05:17:28 EST
Created attachment 273035 [details]
show all three places

rsync'd a project between two machines ('source' to 'target').
on source I had defined a new variable, used in classpath (TOMCAT_HOME_11.0.2)

on target
- the project shows the red excalamtion mark
- Project -> Properties -> Java Build Path -> Libraries shows no error whatsoever!
- Errors view shows a bunch of errors but nothing hinting at the core issue

I'd expect
Project -> Properties -> Java Build Path -> Libraries
to show an error -- after all, the paths/libraries ARE missing. it works with a full path, and thus needs to work with a variable as well
Comment 1 Eclipse Genie CLA 2020-05-27 16:31:02 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.