Bug 530074 - AbstractJavaLaunchConfigurationDelegate.getClasspath is not called
Summary: AbstractJavaLaunchConfigurationDelegate.getClasspath is not called
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.8   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-20 07:01 EST by Igor Fedorenko CLA
Modified: 2022-06-11 13:41 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 2018-01-20 07:01:32 EST 
JUnitLaunchConfigurationDelegate does not call AbstractJavaLaunchConfigurationDelegate.getClasspath in latest 4.8 I-Builds (tried I20180117-2000). This is a breaking API change. Likely introduced by bug #525948, commit https://git.eclipse.org/r/#/c/114634/ to be specific. Let me know if you need more information.
Comment 1 Andrey Loskutov CLA 2018-01-20 09:11:13 EST 
OK, getClasspath() was deprecated and getClasspathAndModulepath() should be used instead. If I understood the change right, the old method was not sufficient thanks to Java 9. Now we have a double-dimensional array (!) which consists of two parts -classpath and module path. 

what about to create getModulePath() method and call the old one and the new one after each other?
Comment 2 Sarika Sinha CLA 2018-01-21 22:46:26 EST 
Check out Bug 529435 also.

We will have to loop through twice if we have two separate methods.
Comment 3 Eclipse Genie CLA 2020-06-20 06:43:57 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 4 Eclipse Genie CLA 2022-06-11 13:41:23 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.