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

Bug 269871

Summary: Linked Jar on build path confuses classpath resolution
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: Olivier_Thomann
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
zipped project none

Description Markus Keller CLA 2009-03-24 14:33:23 EDT
Created attachment 129732 [details]
zipped project

HEAD

- import the attached project into a fresh workspace
- fix the linked file 'moneyLink.jar': Either copy a Jar to 'C:/t/Money/money.jar' on your hard disk, or adjust the link (in the .projects file) to point to another existing Jar.
- open context menu on 'moneyLink.jar' and choose 'Build Path > Add to Build Path'

=> The Java model is confused now:
- misses the folder J/lib (a non-java resource child of the project)
- adds the project 'J' as package fragment root (binary folder) to its own build path

I verified in the JavaElements view that the model is really wrong (it's not a Package Explorer issue or a wrong delta).
Comment 1 Markus Keller CLA 2009-03-24 14:36:17 EDT
Was OK in 3.4.2.
Comment 2 Eclipse Genie CLA 2019-10-14 00:26:41 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.