Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351969 - Wrong error message for AUT configuration problems
Summary: Wrong error message for AUT configuration problems
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 09:20 EDT by Felix Ziesel CLA
Modified: 2019-07-16 07:58 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 Felix Ziesel CLA 2011-07-13 09:20:27 EDT 
If the location of a AUT is wrong (the path could not be found using "executable file name") a wrong error message will occur when the AUT should be started using this configuration:

"AUT could not be started, because no valid Java JRE was specified".
Comment 1 Alexandra Schladebeck CLA 2013-12-13 09:05:07 EST 
This has to do with the fact that the code for our errors for AUT start isn't set up to be able to handle different types of AUT and therefore different reasons. It's one of the things on the list of "to do", but it is definitely a big change.
Comment 2 Eclipse Genie CLA 2015-12-04 00:27:50 EST 
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 Alexandra Schladebeck CLA 2015-12-10 07:18:26 EST 
This has (sadly) been open for very long, and as I understand it, there are some internal reasons why it's not easily fixable.
Comment 4 Eclipse Genie CLA 2017-11-30 03:19:58 EST 
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 5 Marvin Mueller CLA 2019-07-16 07:58:01 EDT 
Since there is no real interest in it closed