Bug 477379 - wrong runtime-classpath when adding projects without sourcefolder
Summary: wrong runtime-classpath when adding projects without sourcefolder
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2015-09-14 11:19 EDT by kurt CLA
Modified: 2022-10-03 17:14 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kurt CLA 2015-09-14 11:19:40 EDT
Adding projects without sourcefolder (only exporting jars) to the runtime-classpath results in adding the exported jars (correct) and wrongly added '\Projectname\bin'.
Where the bin-folder does not exist (because no sourcefolders), and contrary to 'normal' projects, which are added with absolute path, like 'C:\workspace\project\bin', these projects are added with a leading '\' followed by projectname and '\bin'.
Comment 1 Jay Arthanareeswaran CLA 2015-10-15 02:55:33 EDT
I can't reproduce this in master. I can see absolute path being used for both the jar and the bin folder, such as this:

C:\JDT\runtime-New_configuration\Bug477379_1\bin;C:\JDT\runtime-New_configuration\Bug477379_2\ecjRC4.jar

Which build are you using? If you still see it with the latest build, can you attach a testcase or projects where I can see this?
Comment 2 Eclipse Genie CLA 2020-10-03 16:03:33 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 3 Eclipse Genie CLA 2022-10-03 17:14:17 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.