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

Bug 441658

Summary: [IDE] Launch configuration shortens external JAR path and fails
Product: [Eclipse Project] JDT Reporter: arne anka <eclipse-bugs>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P3    
Version: 4.4   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description arne anka CLA 2014-08-13 04:34:54 EDT 
i've got a launch configuration for a Java class which requires another JAR. the JAR belongs to another, rather large, project which ahs been closed (since Edclipse apparently refuses to limit its time consuming refreshing/building and whatever stuff to projects _I_ deem necessary of it -- therefore i closed this project and use its JAR as external JAR with full path

1) add the JAR as External Jar to the lauch configuration's classpath -- it uses the full path starting from /home/user/Workspace/where/the/JAR/lives/my.jar
2) hit run
3) fails with "The archive: /where/the/JAR/lives/my.jar which is referenced by the classpath, does not exist." -- note that path has been shortened to be below Workspace!
4) check lauch configuration's class path and the path has been shortened there too.
5) remove and add again (i'll probably never understnad why i can add and remove entries, but not edit existing ones ...)
6) same game again

looks, like Eclipse again tries to be too smart and, recognizing that this file lies beneath the Workspace, simply shortens its path.
i guess, since the JAR has been added as external, Eclipse tries to access it as absolute path -- or it tries to access it via the _closed_ project, which it is not supposed to do
Comment 1 arne anka CLA 2014-08-13 04:44:10 EDT 
openend the project and now the JAR is found.
seems to boil down to Eclipse stubbornly deciding that any JAR beneath Workspace must not be external, but relative and be resolved via its conating project -- be it closed or not.
Comment 2 Eclipse Genie CLA 2020-03-01 17:44:53 EST 
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.