Note that org.eclipse.equinox.ds is not needed at all; while it's still
available in the p2 repository, it's not longer included in the Eclipse
products/packages. Have you tried not deploying/including it at all?
If I look in a
eclipse\configuration\org.eclipse.equinox.simpleconfigurator\bundles.info
of an Eclipse package such as Committers I see the following at start
level 2 with auto start:
org.apache.felix.scr,2.0.14.v20180822-1822,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.apache.felix.scr_2.0.14.v20180822-1822.jar,2,true
org.eclipse.equinox.common,3.10.200.v20181021-1645,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.equinox.common_3.10.200.v20181021-1645.jar,2,true
org.eclipse.equinox.event,1.5.0.v20181008-1938,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.equinox.event_1.5.0.v20181008-1938.jar,2,true
This at start level 1 auto start:
org.eclipse.equinox.simpleconfigurator,1.3.200.v20181025-1417,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.equinox.simpleconfigurator_1.3.200.v20181025-1417.jar,1,true
Perhaps you might not need this one and it's only need to support updates...
These are also auto started but with "default" start level:
org.eclipse.core.runtime,3.15.100.v20180907-0807,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.core.runtime_3.15.100.v20180907-0807.jar,4,true
org.eclipse.equinox.p2.reconciler.dropins,1.3.0.v20181023-0914,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.equinox.p2.reconciler.dropins_1.3.0.v20181023-0914.jar,4,true
And finally there's this which I guess means it's started really really
early:
org.eclipse.osgi,3.13.200.v20181030-1645,file:/D:/sandbox/USER-HOME/.p2/pool/plugins/org.eclipse.osgi_3.13.200.v20181030-1645.jar,-1,true
Note that there is no org.eclipse.equinox.ds present.
You should be sure that you get all your bundles from a consistent
repository where those bundles are actually used together in
combination, and ensure that the things you actually launch are these
auto start and start level properties.
On 15.03.2019 05:24, Abhijeet Banerjee wrote:
Thanks, Ed,
I tried with upgrading SCR to Level 2 also, but no luck. Just FYI, I
also tried increasing level 3 and 4 too also.
In every case behavior is the same.
Observation: As you told when I am not adding SCR, by default, DS
startLevel was showing 2, with autostart=true.
Now, When I add SCR and change it startLevel=2/3/4 any, I observed DS
startLevel Configuration automatically get reset to blank and vice versa.
When I tried to change DS start level, SCR startLevel and autoStart
get RESET to blank (i.e. No value)
Need some pointer, as I am stuck with no clue
On Thu, Mar 14, 2019 at 11:57 AM Ed Merks <ed.me...@gmail.com
<mailto:ed.me...@gmail.com>> wrote:
In the installer product we set the start levels like this (after
removal of org.eclipse.equinox.ds):
<plugin id="org.eclipse.core.runtime" autoStart="true"
startLevel="4" />
<plugin id="org.eclipse.equinox.common" autoStart="true"
startLevel="2" />
<plugin id="org.apache.felix.scr" autoStart="true"
startLevel="2" />
<plugin id="org.eclipse.equinox.simpleconfigurator"
autoStart="true" startLevel="1" />
With the older platform it used this instead:
<plugin id="org.eclipse.equinox.ds" autoStart="true"
startLevel="2" />
So it seems to me that perhaps it ought to be start level 2...
On 14.03.2019 06:50, Abhijeet Banerjee wrote:
Thanks, Set the level to 1, but No luck.
On Tue, Mar 12, 2019 at 12:23 PM Aleksandar Kurtakov
<akurt...@redhat.com <mailto:akurt...@redhat.com>> wrote:
On Tue, Mar 12, 2019 at 8:51 AM Abhijeet Banerjee
<abhijeet....@gmail.com <mailto:abhijeet....@gmail.com>> wrote:
Thanks, Aleksandar
Felix SCR is in the ACTIVE state, and its included in
bundles.
Is there any other way, that needs to be taken care of?
When you are saying scr should be started, how to check
its started or not (by any cmd) or is there any way
around to start SCR completely
Set felix.scr start level to 1. It has to be started early.
On Tue, Mar 12, 2019 at 12:17 PM Aleksandar Kurtakov
<akurt...@redhat.com <mailto:akurt...@redhat.com>> wrote:
Please make sure felix.scr bundle is started too.
On Tue, Mar 12, 2019 at 8:25 AM Abhijeet Banerjee
<abhijeet....@gmail.com
<mailto:abhijeet....@gmail.com>> wrote:
Greetings,
Currently, I am in the process of upgrading
*/"org.eclipse.osgi.services_3.7.100.v20180827-1536.jar"/*
1. After upgrade during Bundle Validation its
prompt me for 2 Dependent Jar Requirement.
a. */org.eclipse.equinox.ds/*: So
I upgraded my current DS jar with supported
*/"org.eclipse.equinox.ds_1.5.200.v20180827-1235.jar"/*
b. *org.eclipse.osgi.util:* So I
upgraded my current util jar with supported
*/"org.eclipse.osgi.util_3.5.100.v20180827-1536.jar"/*
2. After upgrade of above Step1 Bundle
Validation again prompt for
*/"org.apache.felix.scr"/* missing Jar from
latest*/"equinox.ds_1.5.200"/*
NOTE: Currently my project doesn't contain
this*/("org.apache.felix.scr")/* jar, So I
bundled
*/org.apache.felix.scr_2.0.14.v20180822-1822.jar/*
3. Once all the 3 above mentioned 3PP Jars
Integrated, Bundle Validation stops complaining
no more error,
But when I am trying to run my project its stop
hitting "*updated" *method of
/*@FactoryConfigurationAdapterService*/ and
*/@ServiceDependency f/*rom
org.apache.felix.dependencymanager.annotation-3.2.0".
https://felix.apache.org/apidocs/dependencymanager.annotations/r1/org/apache/felix/dm/annotation/api/FactoryConfigurationAdapterService.html#updated()
Any pointer will be highly appreciated.
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
<mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
--
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
<mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
--
*Thanks\
**Abhijeet Banerjee
+919910512611*
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
--
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
--
*Thanks\
**Abhijeet Banerjee
+919910512611*
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
--
*Thanks\
**Abhijeet Banerjee
+919910512611*
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
