Community
Participate
Working Groups
Using the JEE Eclipse Kepler SR1 bundle, eclipse-jee-kepler-SR1-win32-x86_64.zip, most the of the Jubula functionality is not starting. The Jubula features were installed via the Kepler update site. Some additional features were also installed, but the issue appears to be related to the content of the standard JEE bundle. There appears to be a conflict in the jpa persistence version dependencies. There are two versions, 2.3.2 and 2.5.1. Here are some of the details from the OSGI console: osgi> ss jubula "Framework is launched." id State Bundle 1199 INSTALLED org.eclipse.jubula.app_2.1.1.201309020759 1200 STARTING org.eclipse.jubula.app.autagent_2.1.1.201309020759 1201 STARTING org.eclipse.jubula.app.autrun_2.1.1.201309020759 1202 INSTALLED org.eclipse.jubula.app.cmd_2.1.1.201309020759 1203 INSTALLED org.eclipse.jubula.app.dbtool_2.1.1.201309020759 1204 STARTING org.eclipse.jubula.autagent_2.1.1.201309020759 1205 STARTING org.eclipse.jubula.client.analyze_2.1.1.201309020759 1206 INSTALLED org.eclipse.jubula.client.analyze.impl.standard_2.1.1.201309020759 1207 INSTALLED org.eclipse.jubula.client.analyze.ui_2.1.1.201309020759 1208 INSTALLED org.eclipse.jubula.client.archive_2.1.1.201309020759 1209 INSTALLED org.eclipse.jubula.client.autagent_2.1.1.201309020759 1210 INSTALLED org.eclipse.jubula.client.cmd_2.1.1.201309020759 1211 RESOLVED org.eclipse.jubula.client.cmd.controller_2.1.1.201309020759 1212 INSTALLED org.eclipse.jubula.client.core_2.1.1.201309020759 1213 INSTALLED org.eclipse.jubula.client.inspector.ui_2.1.1.201309020759 1214 INSTALLED org.eclipse.jubula.client.teststyle_2.1.1.201309020759 1215 INSTALLED org.eclipse.jubula.client.teststyle.impl.standard_2.1.1.201309020759 1216 RESOLVED org.eclipse.jubula.client.ua.cheatsheets_2.1.1.201309020759 1217 STARTING org.eclipse.jubula.client.ua.help_2.1.1.201309020759 1218 RESOLVED org.eclipse.jubula.client.ua.welcome_2.1.1.201309020759 1219 INSTALLED org.eclipse.jubula.client.ui_2.1.1.201309020759 1220 INSTALLED org.eclipse.jubula.client.ui.rcp_2.1.1.201309020759 1221 RESOLVED org.eclipse.jubula.communication_2.1.1.201309020759 1222 INSTALLED org.eclipse.jubula.launch_2.1.1.201309020759 1223 INSTALLED org.eclipse.jubula.launch.java_2.1.1.201309020759 1224 INSTALLED org.eclipse.jubula.launch.java.ui_2.1.1.201309020759 1225 INSTALLED org.eclipse.jubula.launch.rcp.ui_2.1.1.201309020759 1226 INSTALLED org.eclipse.jubula.launch.ui_2.1.1.201309020759 1227 RESOLVED org.eclipse.jubula.rc.common_2.1.1.201309020759 1228 RESOLVED org.eclipse.jubula.rc.common.agent_2.1.1.201309020759 1229 RESOLVED org.eclipse.jubula.rc.rcp_2.1.1.201309020759 1230 RESOLVED org.eclipse.jubula.rc.swing_2.1.1.201309020759 1231 RESOLVED org.eclipse.jubula.rc.swt_2.1.1.201309020759 1232 STARTING org.eclipse.jubula.toolkit.common_2.1.1.201309020759 1233 STARTING org.eclipse.jubula.toolkit.provider.base_2.1.1.201309020759 1234 STARTING org.eclipse.jubula.toolkit.provider.concrete_2.1.1.201309020759 1235 INSTALLED org.eclipse.jubula.toolkit.provider.html_2.1.1.201309020759 1236 INSTALLED org.eclipse.jubula.toolkit.provider.rcp_2.1.1.201309020759 1237 INSTALLED org.eclipse.jubula.toolkit.provider.rcp.gef_2.1.1.201309020759 1238 STARTING org.eclipse.jubula.toolkit.provider.swing_2.1.1.201309020759 1239 INSTALLED org.eclipse.jubula.toolkit.provider.swt_2.1.1.201309020759 1240 RESOLVED org.eclipse.jubula.tools_2.1.1.201309020759 1241 STARTING org.eclipse.jubula.ui.compatibility_2.1.1.201309020759 osgi> diag 1212 reference:file:plugins/org.eclipse.jubula.client.core_2.1.1.201309020759.jar [1212] Package uses conflict: Require-Bundle: org.eclipse.persistence.jpa; bundle-version="[2.3.0,2.4.0)" Package uses conflict: Require-Bundle: org.eclipse.persistence.jpa.osgi; bundle-version="[2.3.0,2.4.0)" osgi> ss persistence "Framework is launched." id State Bundle 18 RESOLVED javax.persistence_2.1.0.v201304241213 610 RESOLVED org.eclipse.persistence.antlr_3.2.0.v201302191141 611 RESOLVED org.eclipse.persistence.asm_3.3.1.v201302191223 612 RESOLVED org.eclipse.persistence.core_2.5.1.v20130824-981335c Fragments=1249 613 RESOLVED org.eclipse.persistence.dbws_2.5.1.v20130824-981335c 614 RESOLVED org.eclipse.persistence.dbws.builder_2.5.1.v20130824-981335c 615 RESOLVED org.eclipse.persistence.jpa_2.5.1.v20130824-981335c 616 RESOLVED org.eclipse.persistence.jpa.jpql_2.5.1.v20130824-981335c 617 RESOLVED org.eclipse.persistence.moxy_2.5.1.v20130824-981335c 1192 RESOLVED javax.persistence_2.0.3.v201010191057 1243 RESOLVED org.eclipse.persistence.antlr_2.3.2.v20111125-r10461 1244 RESOLVED org.eclipse.persistence.asm_2.3.2.v20111125-r10461 1245 RESOLVED org.eclipse.persistence.core_2.3.2.v20111125-r10461 1246 RESOLVED org.eclipse.persistence.jpa_2.3.2.v20111125-r10461 1247 RESOLVED org.eclipse.persistence.jpa.jpql_1.0.1.v20111125-r10461 1248 RESOLVED org.eclipse.persistence.jpa.osgi_2.3.2.v20111125-r10461
This issue seems to be related to the closed Bug 407730 - "Eclipse for Testers - Kepler RC1 : majority of Jubula core bundles don't start".
I wonder if this is also related to bug 416237.
Bug 416237 appears to be a duplicate of this. My investigation on the OSGI state appears to indicate the root cause to be JPA persistence version incompatibilities. Moving Jubula to the 2.5.1 version should solve the issue. Jubula should be dependent on the version which is part of the simultaneous release. Perhaps there is some technical reason it was not updated. A simple Jubula feature installation onto the most popular Eclipse bundles would be a good addition to pre-release tests. For my development group, this is the second time we have not been able to install Jubula into a standard Eclipse bundle (due to dependency conflicts) and had to use a separate stand-alone installation for the Jubula capabilities. This type of testing would help to prevent this again in the future. I believe the runtime test execution agent plugins are activating, which means tests can be executed with the bundle (this should be confirmed); however, the UI components for writing the tests do not start which means a separate bundle is needed for those activities. As a result, the issue can be worked around until the dependency for the persistence relating to the UI features is sorted out.
Thanks for the comments Bryan. I know that there is a reason why we use an older version of the JPA persistance, but I'll let someone more qualified from the team comment further.
We currently need an older version of EclipseLink to run properly, otherwise we get some really strange update problems. We are not yet able to make a simple reproducible example of this problem. Therefore we are stuck with the older version. Unfortunately this version of EclipseLink will not run with the currently supplied JPA API. We are still working on either getting the problem fixed or finding a proper workaround.
*** Bug 416237 has been marked as a duplicate of this bug. ***
Just for the record: bug 407889 describes the problem of using an old version of EclipseLink.
Since the related ticket is closed fixed, I'm resolving this as fixed too.
Closed due to comments 6 - 8
