Eclipse Community Forums: Jubula » different unbound_module versions in standalone and eclipse plugin

Help

Home

Home » Archived » Jubula » different unbound_module versions in standalone and eclipse plugin

Show: Today's Messages :: Show Polls :: Message Navigator

different unbound_module versions in standalone and eclipse plugin [message #1151636]

Wed, 23 October 2013 13:43

Sascha Winkler

Messages: 30
Registered: March 2013

Member

Hey,

I want to share my testcases (created with the jubula standalone) with another team member, but he used the eclipse plugin. The problem is that the eclipse-plugin of jubula (version 2.1.0xxx) used the unbound-modules at version 7.1. At my standalone jubula (version 7.2) the same modules are only at 7.0
Before I had the 7.1 standalone client, which also used the unbound-modules in version 7.0.

Is there a way to share my testcases (without installing the standalone on the other machine)? why are there used different versions for the standalone and the plugin jubula?

best regards,
Sascha

EDIT: I'm sorry. There went something wrong. now the unbound_modules in the standalone are at version 7.2. In the plugin is still version 7.1. Have we missed a update for the jubula plugin?

[Updated on: Wed, 23 October 2013 14:56]

Report message to a moderator

Re: different unbound_module versions in standalone and eclipse plugin [message #1153152 is a reply to message #1151636]

Thu, 24 October 2013 12:15

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi Sascha,

The Jubula plugin via Eclipse for Testers was released with the Kepler SR1 release, and the standalone version 7.2 is newer, so the current Eclipse for Testers / Standalone versions are out-of-sync. Since the database versions are different, both can't be used at the same time for the same project.

Best regards,
Alex

Report message to a moderator