Am 19.07.2010 17:44, schrieb Andrea Zoppello:
osgi.bundles=org.eclipse.equinox.common@2:start,\
org.eclipse.update.configurator@start,\
ch.qos.logback.classic@4:start,\
ch.qos.logback.core@4:start,\
ch.qos.logback.slf4j@4:start,\ <- This is the fragment bunlde i've put
a line saying to start even if is not correct this seems to cause a
"correct resolution"
In your 'osgi.bundles' configuration the
'org.eclipse.update.configurator' is responsible for managing the
bundles in the framework. Thus, it should have found an installed it.
The Logback/SLF4J bundles don't need to be started. They don't have an
activator.
The following should work:
osgi.bundles=org.eclipse.equinox.common@2:start,\
org.eclipse.update.configurator@start
I'm not sure about the following, but AFAIK it should install the
bundles but don't start them:
osgi.bundles=org.eclipse.equinox.common@2:start,\
org.eclipse.update.configurator@start,\
ch.qos.logback.classic,\
ch.qos.logback.core,\
ch.qos.logback.slf4j,\
FWIW, I switched to p2 based deployments on servers. They don't use
'org.eclipse.update.configurator' but work with the (more reliable) p2
simpleconfigurator.
-Gunnar
--
Andrea Zoppello
Spagic Architect
|
Respect
the environment. Please don't print this e-mail unless you really need
to. |
The information transmitted is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance
upon, this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.