Eclipse Community Forums: Virgo » A bundle could not be resolved

Home » Eclipse Projects » Virgo » A bundle could not be resolved(the required execution enviroment did not match the runtime environment.)

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

A bundle could not be resolved [message #754867]

Fri, 04 November 2011 16:58

Geoffry Roberts

Messages: 29
Registered: March 2011

Junior Member

All,

Two dependencies are complaining. I am using JDK6. A quick peek at the manifests in the dependencies show they require JDK4 as a minimum.

If JDK4 is the minimum version required why the error over JDK6?

I pulled these two bundles from eclipse/plugins.

A bundle could not be resolved because the required execution enviroment did not match the runtime environment. In bundle <o
rg.apache.xerces_2.9.0.v201101211617>
        A bundle could not be resolved because the required execution enviroment did not match the runtime environment. In bundle <o
rg.apache.xml.serializer_2.7.1.v201005080400>

Report message to a moderator

Re: A bundle could not be resolved [message #754947 is a reply to message #754867]

Sat, 05 November 2011 17:52

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

The xerces bundle you mention contains the following in its manifest:

Bundle-RequiredExecutionEnvironment: J2SE-1.2

and not J2SE-1.4. Please double-check the manifest.

Virgo's profile (lib/java6-server.profile) defines the following execution environments:

org.osgi.framework.executionenvironment = \
OSGi/Minimum-1.0,\
OSGi/Minimum-1.1,\
J2SE-1.3,\
J2SE-1.4,\
J2SE-1.5,\
JavaSE-1.6

There is no assumption that J2SE-1.4 covers J2SE-1.2, which is why you get a resolution error. If you want to make that assumption, add J2SE-1.2 to the above property.

Report message to a moderator

Re: A bundle could not be resolved [message #755248 is a reply to message #754867]

Mon, 07 November 2011 19:09

Geoffry Roberts

Messages: 29
Registered: March 2011

Junior Member

Thanks again, clearly I misread the manifest in question. The real help was learning about the java6-server.profile file. I made the entry you recommended and that problem ceased.

Now I have another problem. What is hapi.plan-1-synthetic.context. It appears to have something to do with gemini's attempt to deploy my plan, which is called hapi.plan.

I don't understand how to interpret the following error.

[2011-11-07 10:35:12.540] fs-watcher                   <DE0002E> Installation of plan 'hapi.plan' version '1.0.0' failed. org.eclips
e.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'hapi.plan-1-synt
hetic.context' at version '1.0.0': Cannot resolve: hapi.plan-1-synthetic.context
    Resolver report:
        Uses violation: <Import-Package: org.eclipse.gemini.blueprint.context.support; version="0.0.0"> in bundle <hapi.plan-1-synth
etic.context_1.0.0[1320690856875]>
             Resolver reported uses conflict for import constrained to bundle <hapi.plan-1-org.eclipse.gemini.blueprint.core> constr
ained bundle version range "[1.0.0.RELEASE,1.0.0.RELEASE]"
            with attributes {module_scope=hapi.plan-1}

Report message to a moderator

Re: A bundle could not be resolved [message #755405 is a reply to message #755248]

Tue, 08 November 2011 11:23

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

Uses constraints are described in the FAQ. The synthetic context bundle is described in the Programmer Guide - search for "synthetic".

Uses constraint failures in resolving the synthetic context bundle are pretty rare - I don't remember seeing one before. So presumably you have transitive dependencies on multiple versions of the same package. The FAQ will give you some ideas for how to diagnose this.

Report message to a moderator

Previous Topic:	bundle full path file name
Next Topic:	using the eclipse runtime in virgo

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 02 07:24:17 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter