Bug 538823 - "Command line cannot be retrieved" for standalone JUnit launch
Summary: "Command line cannot be retrieved" for standalone JUnit launch
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-08 07:18 EDT by Ed Willink CLA
Modified: 2023-03-18 12:19 EDT (History)
2 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 Ed Willink CLA 2018-09-08 07:18:20 EDT 
Using the new "Show Command line" facility for

GIT\org.eclipse.ocl\tests\org.eclipse.ocl.examples.xtext.tests\.settings\org.eclipse.ocl.examples.xtext.tests (standalone).launch

gives "Command line cannot be retrieved" in the pop-up.

(Launch is a JavaSE 1.8 which is mapped to Java 10.0.2)
Comment 1 Sarika Sinha CLA 2018-09-10 00:28:02 EDT 
Can you check which Junit is it using? 
And are you able to run in that case?

I saw this case and it looked Junit issue rather than displaying command line issue.
Comment 2 Ed Willink CLA 2018-09-10 01:12:35 EDT 
The TestRunner is set to JUnit 4.

It is a test case I have been running for many years.

(Even if it could not run, surely there should be a failure reason / stack trace?)
Comment 3 Sarika Sinha CLA 2018-09-10 01:16:39 EDT 
(In reply to Ed Willink from comment #2)
> The TestRunner is set to JUnit 4.
> 
> It is a test case I have been running for many years.
> 
> (Even if it could not run, surely there should be a failure reason / stack
> trace?)

So does it fail in run ?
Currently the scope of Show Command line is not to show the reason of failure.
Comment 4 Ed Willink CLA 2018-09-10 01:18:02 EDT 
(In reply to Sarika Sinha from comment #3)
> (In reply to Ed Willink from comment #2)
> > It is a test case I have been running for many years.

And it still works fine.
Comment 5 Sarika Sinha CLA 2018-09-10 01:32:17 EDT 
Is there any error printed in the error log? 
Can you attach the sample testcase so that I can reproduce ?
Comment 6 Eclipse Genie CLA 2020-09-18 16:03:16 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 7 Eclipse Genie CLA 2023-03-18 12:19:25 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.