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

Bug 355083

Summary:	Version check for RC RCP Plugin
Product:	[Technology] Jubula	Reporter:	Alexandra Schladebeck <alexandra.schladebeck>
Component:	RC	Assignee:	Project Inbox <jubula.rc-inbox>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	enhancement
Priority:	P1	CC:	tombrus
Version:	1.0.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Alexandra Schladebeck

2011-08-18 09:38:49 EDT

After a version change, the version of the RC Plugin for RCP must be changed in the AUT. Not doing this can result in strange errors (timeouts, odd behaviour, not being able to map etc) and whenever this happens time is lost looking for the cause of the problem. It would be great if the version of the RCP plugin in the AUT could be checked to see if it is the correct one, and a warning shown if it is not. This would save a lot of time and confusion when migrating.

Comment 1 Tom Brus

2011-08-18 09:47:41 EDT

I would suggest to generate an error message instead of a warning if the versions of the RCP plugin are incompatible. It would be no use continuing the test.

Comment 2 Alexandra Schladebeck

2011-10-07 08:21:50 EDT

An initial implementation for this has now been done. If the RC Plugin is not the correct version, the AUT is ended and a message is written into the log. This isn't as well-rounded as it could be, but it does mean that we now have a defined behaviour as well as a place to read what the problem was. This is in the currently released version (1.1), but will only be useful from the next version, when the RC RCP Plugin changes again.