Bugzilla – Full Text Bug Listing
| Summary: | external classpath entries in .launch config auto converted to project paths | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ilya Basin <basinilya> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | loskutov | ||||
| Version: | 4.11 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
I assume the "external" path you enter matches exactly a path inside your project? Please try with 4.13. What happens if you manually change the config on disk, will it be automatically updated? (In reply to Andrey Loskutov from comment #1) > I assume the "external" path you enter matches exactly a path inside your > project? > > Please try with 4.13. What happens if you manually change the config on > disk, will it be automatically updated? I see no difference between 4.13 and 4.11. If I manually change the entry it stays external until I try to edit it again in Eclipse. 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. 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. |
Created attachment 279908 [details] screenshot For a certain test I need a launch configuration without the default project classpath and instead launches a .jar file in a project output directory "bin/". Don't ask why it's there. I add this jar as external jar to the launch config, however, Eclipse is being too smart and automatically converts the external jar to a project-relative path. As the result, I get the following error dialog when trying to launch: The archive: /testexternal/bin/aaa.jar which is referenced by the classpath, does not exist. Look, if I wanted a relative path, I would do that myself. What problem does Eclipse try to solve by this conversion? In my opinion this feature should be removed.