Community
Participate
Working Groups
Eclipse for Testers - Kepler M7 does not work at all (at least on Mac OS X) due to: ==== osgi> diag 187 reference:file:plugins/org.eclipse.jubula.client.core_2.1.0.201305061353.jar [187] Direct constraints which are unresolved: Missing required bundle org.eclipse.persistence.jpa.osgi_[2.2.0,3.0.0). Leaf constraints in the dependency chain which are unresolved: reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [269] Missing imported package javax.persistence.spi_[1.1.0,2.2.0). reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [269] Missing imported package javax.persistence_[1.1.0,2.2.0). reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [269] Missing imported package javax.persistence.criteria_[1.1.0,2.2.0). reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [269] Missing imported package javax.persistence.metamodel_[1.1.0,2.2.0). osgi> ss persistence "Framework is launched." id State Bundle 14 ACTIVE javax.persistence_2.1.0.v201304241213 264 RESOLVED org.eclipse.persistence.antlr_3.2.0.v201302191141 265 RESOLVED org.eclipse.persistence.asm_3.3.1.v201302191223 266 RESOLVED org.eclipse.persistence.core_2.5.0.v20130425-368d603 Fragments=270 267 RESOLVED org.eclipse.persistence.jpa_2.5.0.v20130425-368d603 268 RESOLVED org.eclipse.persistence.jpa.jpql_2.5.0.v20130425-368d603 269 INSTALLED org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345 270 RESOLVED org.eclipse.persistence.oracle_2.5.0.v20130403-3bb7011 Master=266
For some reason I don't see the error here. It must have something to do with bundle org.eclipse.persistence.jpa.osgi because this complains about missing dependencies that cannot be resolved: org.eclipse.persistence.jpa.osgi osgi> diag 268 reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [268] Direct constraints which are unresolved: Missing imported package javax.persistence_[1.1.0,2.2.0). Missing imported package javax.persistence.criteria_[1.1.0,2.2.0). Missing imported package javax.persistence.metamodel_[1.1.0,2.2.0). Missing imported package javax.persistence.spi_[1.1.0,2.2.0). If I am trying to start it manually from the console, it behaves as expected and throws an error: osgi> start 268 gogo: BundleException: The bundle "org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345 [268]" could not be resolved. Reason: Missing Constraint: Import-Package: javax.persistence; version="[1.1.0,2.2.0)" But the mystery starts when I look at the bundle that is supposed to export all the required packages. The above bundle complains about javax.persistence in version >=1.1.0 and <2.2.0, but the bundle below exports this package in version 2.1.0. What am I missing here? osgi> bundle javax.persistence javax.persistence_2.1.0.v201304241213 [14] Id=14, Status=ACTIVE Data Root=/tmp/eclipse/configuration/org.eclipse.osgi/bundles/14/data "No registered services." No services in use. Exported packages javax.persistence; version="2.1.0"[exported] javax.persistence.criteria; version="2.1.0"[exported] javax.persistence.metamodel; version="2.1.0"[exported] javax.persistence.spi; version="2.1.0"[exported] org.osgi.service.jpa; version="1.1.0"[exported] Imported packages org.osgi.framework; version="1.7.0"<org.eclipse.osgi_3.9.0.v20130410-1557 [0]> javax.sql; version="0.0.0"<org.eclipse.osgi_3.9.0.v20130410-1557 [0]> No fragment bundles Named class space javax.persistence; bundle-version="2.1.0.v201304241213"[provided] No required bundles I'd suggest you work with the EclipseLink people to resolve this issue.
(In reply to comment #1) > osgi> diag 268 > reference:file:plugins/org.eclipse.persistence.jpa.osgi_2.4.1.v20121003-ad44345.jar [268] That bundle has a surprisingly old timestamp in its qualifier (oct 2012), is that expected ?
Thank you for the additional comments / information - I'm investigating.
It seems that this issue is caused by actions taken for bug 398410. AFAICS the version constrains mystery (not being resolved though >=1.1.0 and <2.2.0) is caused by a JPA-"version bound" version dependency Information taken from the corresponding MANIFEST.MF files: === org.eclipse.persistence.jpa.osgi == 2.4.1.v20121003-ad44345 == Import-Package: javax.persistence;jpa="2.0";version="[1.1.0,2.2)" ... === Bundle-SymbolicName: javax.persistence == 2.1.0.v201304241213 == Export-Package: javax.persistence;jpa="2.1";version="2.1.0"
@Triaged:+ Like discussed this morning this is a "must fix soon."
This issue is caused by using and mixing bundles (as e.g. also mentioned in comment 2) of no-longer existing API in EclipseLink 2.4 and 2.5 - tracking this deprecated API usage with bug 407889.
We should discuss whether we want to a) for now continue using the deprecated API for the upcoming Kepler release and bundle our own version of EclipseLink JPA OSGi support b) or fix the deprecated API usage (bug 407889)
After an evaluation of path b) (see bug 407889 comment 2 and 3) we decided to give (the temporary) solution a) a chance.
The bundles we require and are now about to be maintained by ourselves have been removed with commit [1]. [1] http://git.eclipse.org/c/eclipselink/eclipselink.runtime.git/commit/?h=2.5&id=3f8ee56021cf172af7dda7e7cbc6b919a932f06c
No longer maintained "org.eclipse.persistence.jpa.osgi" bundle has been adapted (moved renamed to org.eclipse.jubula.persistence.jpa.osgi) and applied for EclipseLink 2.5 usage with changeset [1]. It is *not* intended to be used by anyone but ourselves as this is only supposed to be a temporary solution. [1] http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=faa43cb7876b7ca9334afc97571a3b407525b634
Resolving this issue as described in comment 10 does now cause (IMO due to the change to EclipseLink 2.5) bug 408103. In addition to that we face bug 399726 and bug 399729 since using EclipseLink 2.4 - my silent wish has been that switching to EL 2.5 also resolves those issue. Since this is not the case we've now decided to switch back to EL 2.3.2 and bundle this specific version within Jubula / Eclipse for Testers. This - at least for now - does also make the workaround implement with changeset from comment 10 obsolete.
Modifications mentioned for comment 11 have been applied with changeset: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=2249f6854dc78e5345079d52a0a7e708e9e8de13 In addition to that I removed the explicit feature dependency to "org.eclipse.persistence.jpa" from the EPP testing feature with changeset: http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=310af9317f6c0e296edfbf6f24914f2d8e8ad745 We do now package the (hopefully correct) versions of the EclipseLink JPA bundles within the Jubula feature itself.
I've just downloaded RC1, and the same symptom is occurring. I can see the cheat sheets and the welcome pages, and the docu is there. However, none of the perspectives or the Jubula features / plugins are present.
The problem seems to be pretty much the same: again our "org.eclipse.jubula.client.core"-bundle does not get started, this time due to "Package uses conflict": osgi> diag 191 reference:file:plugins/org.eclipse.jubula.client.core_2.1.0.201305220921.jar [191] Package uses conflict: Require-Bundle: org.eclipse.persistence.core; bundle-version="[2.3.0,2.4.0)" Package uses conflict: Require-Bundle: org.eclipse.persistence.jpa; bundle-version="[2.3.0,2.4.0)" I'm investigating.
AFAICS the presence of the "javax.transaction" bundle in version "1.1.0.v201205091237" is causing this issue. Due to this and the "org.eclipse.osgi" bundle in version "3.9.0" multiple provider for the package "javax.transaction" are present. Disabling / removing the "javax.transaction" seems to resolve this issue while keeping everything else running.
FYI: the only way to track this issue down was to debug the OSGi resolving mechanism (see bug 292774) for further information on better tooling support. The resolving magic is happening in "org.eclipse.osgi.internal.module.ResolverImpl". Especially debugging / setting breakpoints in "addConflicts(...)" and "getConflicts(...)" helped me a lot.
As bug 409122 has been resolved please regression test this one asap or at least for Kepler RC2.
As long as bug 409122 has been already verified and closed, I close this bug, too.
