Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346863 - Not possible to open AUT Configuration in Jubula after export project from GUIdancer
Summary: Not possible to open AUT Configuration in Jubula after export project from GU...
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Indigo RC3   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 08:46 EDT by Tim Winselmann CLA
Modified: 2011-05-30 08:15 EDT (History)
2 users (show)

See Also:

Attachments
Stacktrace from the Client log (9.58 KB, application/octet-stream)
2011-05-23 08:46 EDT, Tim Winselmann CLA 		no flags Details
Stacktrace from the Client log as text file (9.58 KB, text/plain)
2011-05-23 08:48 EDT, Tim Winselmann CLA 		no flags Details
Show Obsolete (1) View All 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 Tim Winselmann CLA 2011-05-23 08:46:13 EDT 
Created attachment 196326 [details]
Stacktrace from the Client log

After the successful import of a project it is not possible an open one AUT Configuration. The project was exported by GUIdancer and the AUT Configuration has a Monitoring Agent specified. 

The error message is "3015: The selected AUT cannot be configured because the AUTs Toolkit could not be found."

After this error message an empty Configuration page appears.

I have attached the stacktrace from the Client log.
Comment 1 Tim Winselmann CLA 2011-05-23 08:48:42 EDT 
Created attachment 196329 [details]
Stacktrace from the Client log as text file
Comment 3 Oliver Goetz CLA 2011-05-30 08:15:03 EDT 
Verified manually using jubula-nightly May 30, 2011