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

Bug 508495

Summary:	Debug runs with large classpaths include project root directory when they should not
Product:	[Eclipse Project] JDT	Reporter:	David Cowan <david>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Michael_Rennie, sarika.sinha
Version:	4.6
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:	stalebug

Description David Cowan

2016-11-30 15:29:11 EST

Bug 327193 fixed an issue with debug runs not working in windows for command lines over 32k characters.  To do this the env variable CLASSPATH is used once commands get to large.  When this is done instead of using the -classpath switch no -classpath is passed and CLASSPATH env variable is used.  The problem with this is that the jvm by default appends a default classpath of the working directory if -classpath is not used.  This had the nasty side effect for me of my run working as expected and not having the project root directory into the classpath until I finally had enough libraries included to break over 32k and suddenly my classpath now includes the root project dir which brings in a classpath I do not want or expect.

Comment 1 Sarika Sinha

2016-11-30 22:25:48 EST

@Mike,
Do you want to add anything ?

Comment 2 Eclipse Genie

2020-04-12 19:18:48 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. 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.