Katya's right, the problem is likely at 'publishing' time, but you're only seeing the effects at install/deploy time.
Check the content.jar file that your build produced and look for the simpleConfigurator. Check if it has a startLevel set. Do you specify your own config.ini file at build time? I suspect that if you do, it might conflict with PDE/Build trying to set the start level for known bundles. Cheers, Ian On Thu, Oct 27, 2011 at 1:49 AM, Todorova, Katya <[email protected]>wrote: > You have all the bundles listed in config.ini instead of bundles.infobecause > for some reason the “configuration unit” for simple configurator in > your product file is not taken into account during the update. **** > > This also leads to changing sc start level from 1 to 4 and sc start mode > from “started” to “not started” (the default behavior) and respectively to > the issue you described below.**** > > ** ** > > What you could do is checking whether simple configurator’s CU (usually > named “tooling<your_OS_arch>org.eclipse.equinox.simpleconfigurator”) is :* > *** > > **· **presented in your product repository**** > > **· **required by your product**** > > ** ** > > As for manual editing of config.ini – as the other guys already said – it > shouldn’t be done because after that you cannot guarantee the consistency of > your system. p2 would do that for you if you set all your **** > > properties via corresponding touchpoint actions and get rid of shipping the > file with your product. I believe this error message:**** > > org.osgi.framework.BundleException: The bundle > "org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525 [302]" could not > be resolved. **** > > Reason: Another singleton version selected: > org.eclipse.equinox.p2.reconciler.dropins_1.1.2.R36x_v20110114 > is an illustration of system inconsistency after manual interaction with > config.ini.**** > > ** ** > > Hope this helps. **** > > ** ** > > Kind regards,**** > > Katya**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Samuel Wu > *Sent:* mercredi 26 octobre 2011 22:35 > *To:* P2 developer discussions > *Subject:* Re: [p2-dev] Is there a way to update the file config.ini?**** > > ** ** > > The following is the whole config.ini before the update. > > org.eclipse.update.reconcile=false > eclipse.p2.profile=profile > [email protected]/workspace > osgi.framework=file\:plugins/org.eclipse.osgi_3.6.1.R36x_v20100806.jar > equinox.use.ds=true > eclipse.buildId=I20100729-1656 > > osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@1 > \:start > > org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/ > bundles.info > eclipse.product=com.ibm.tpf.toolkit.productm > > osgi.splashPath=platform\:/base/plugins/com.ent.customized.toolkit.branding,platform\:/base/plugins/com.ibm.tpf.toolkit,platform\:/base/plugins/com.ibm.tpf.toolkit.nl1, > platform\:/base/plugins/org.eclipse.platform > osgi.framework.extensions= > osgi.bundles.defaultStartLevel=4 > eclipse.application=org.eclipse.ui.ide.workbench > [email protected]/../p2/ > eof=eof > > > Attribute org.eclipse.equinox.simpleconfigurator.configUrl contains the > simple configurator and it kept unchanged during the update. > The only changed one was osgi.bundles. The problem is not that other > bundles were added to the list. The problem is that it changed the start > level from 1 to 4. It was set to 1 in the product file. > > > Best Regards > > Samuel Wu > > > [image: Inactive hide details for DJ Houghton---10/26/2011 03:22:14 PM---I > can't remember the exact details, but this basically means t]DJ > Houghton---10/26/2011 03:22:14 PM---I can't remember the exact details, but > this basically means that your product isn't configured corr**** > > > From:**** > > > DJ Houghton/Ottawa/IBM@IBMCA**** > > > To:**** > > > P2 developer discussions <[email protected]>**** > > > Date:**** > > > 10/26/2011 03:22 PM**** > > > Subject:**** > > > Re: [p2-dev] Is there a way to update the file config.ini?**** > > > Sent by:**** > > > [email protected]**** > ------------------------------ > > > > > I can't remember the exact details, but this basically means that your > product isn't configured correctly so when framework admin goes to write out > the config.ini file, it has to write out all the bundles in your product > rather than just the simple configurator. > > You should not be editing this list, it should be managed by p2. > > Do you have any other simple configurator-related properties in your > config.ini file? > > > [image: Inactive hide details for Samuel Wu---2011/10/26 11:09:34 AM---Hi > DJ, We currently have the following attribute in our config.i]Samuel > Wu---2011/10/26 11:09:34 AM---Hi DJ, We currently have the following > attribute in our config.ini.**** > > > From:**** > > > Samuel Wu/Toronto/IBM@IBMCA**** > > > To:**** > > > P2 developer discussions <[email protected]>**** > > > Date:**** > > > 2011/10/26 11:09 AM**** > > > Subject:**** > > > Re: [p2-dev] Is there a way to update the file config.ini?**** > > > Sent by:**** > > > [email protected]**** > ------------------------------ > > > > > Hi DJ, > > We currently have the following attribute in our config.ini. > > osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@1 > \:start > > While updating the product, the config.ini was changed to contain the > following attribute. > > osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@4 > ,reference\:file\:com.ibm.cdz.branding_1.6.2.201107272117.jar@4 > ,reference\:file\:com.ibm.cdz.common_1.6.2.201107272117.jar@4 > ,reference\:file\:com.ibm.cdz.remote.cshelp_1.6.2.201108112140.jar@4 > ,reference\:file\:com.ibm.cdz.remote.doc_1.6.2.201108160029.jar@4 > ,reference\:file\:com.ibm.debug.daemon_7.0.400.v20110207_2130.jar@4 > ,reference\:file\:com.ibm.debug.daemon.cshelp_7.0.1.v20080702.jar@4 > ,reference\:file\:com.ibm.debug.idebug.doc.tpf_1.0.1.v20110315_1958.jar@4 > ,reference\:file\:com.ibm.debug.idebug.tpf.cshelp_1.0.2.v20080919.jar@4 > ,reference\:file\:com.ibm.debug.idebug.tpf.cslink_1.0.3.v20101019_1137.jar@4 > ,reference\:file\:com.ibm.debug.memorymap_7.2.213.v20110307_0400.jar@4 > ,reference\:file\:com.ibm.debug.memorymap.cshelp_7.0.0.v20071102a.jar@4 > ,reference\:file\:com.ibm.debug.memorymap.doc_7.0.0.v20080723.jar@4 > ,reference\:file\:com.ibm.debug.memoryoffset_7.1.12.v20110307_0400.jar@4 > ,reference\:file\:com.ibm.debug.memoryoffset.cshelp_7.0.0.v20071102a.jar@4 > ,reference\:file\:com.ibm.debug.pdt_7.3.11.v20100629_1840.jar@4 > ,reference\:file\:com.ibm.debug.pdt.animatedstep_1.1.103.v20110318_1505.jar@4 > ,reference\:file\:com.ibm.debug.pdt.common_7.3.1.v20110131_2003.jar@4 > ,reference\:file\:com.ibm.debug.pdt.core_8.2.1.v20110318_1505.jar@4 > ,reference\:file\:com.ibm.debug.pdt.engines.tpf_1.0.0.v20100922_1443/@4,reference\:file\:com.ibm.debug.pdt.migration_1.1.0.v20101027_1400.jar@4 > ,reference\:file\:com.ibm.debug.pdt.remotebrowse_7.1.102.v20101019_1137.jar@4 > ,reference\:file\:com.ibm.debug.pdt.rsecommon_7.2.12.v20101027_1400.jar@4 > ,reference\:file\:com.ibm.debug.pdt.ui_8.2.1.v20110318_1505.jar@4 > ,reference\:file\:com.ibm.eNetwork.beans.HOD_11.0.3.201102241514/@4,reference\:file\:com.ibm.editors.swtbidiextension_1.1.2.201008101158/@4,reference\:file\:com.ibm.etools.common.navigator_3.6.0.201010140900.jar@4 > ,reference\:file\:com.ibm.etools.hasslite_1.0.2.201006150117/@4,reference\:file\:com.ibm.etools.host.connect_8.0.100.v20110414_1721.jar@4 > ,reference\:file\:com.ibm.etools.icerse.editable_3.0.0.v20100413_1531.jar@4 > ,reference\:file\:com.ibm.etools.icerse.editor_.... > osgi.bundles now contains a long list of all the features. > We cam start our product with this config.ini. The following error messages > were generated in the log file. > org.osgi.framework.BundleException: The bundle > "org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525 [302]" could not > be resolved. Reason: Another singleton version selected: > org.eclipse.equinox.p2.reconciler.dropins_1.1.2.R36x_v20110114 > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317) > ...... > java.lang.IllegalStateException: Unable to acquire application service. > Ensure that the org.eclipse.core.runtime bundle is resolved and started (see > config.ini). > at > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) > .... > > We found that if we change the attribute to the following ones. It started > to work. > > osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@1 > \:start > > I noticed there are a few touchpoint actions which allow you to change the > options. Which one can be use to fix this one? Thanks. > > Best Regards > > Samuel Wu > > > [image: Inactive hide details for DJ Houghton---10/26/2011 09:56:25 > AM---The file is most likely updated when the reconciler is run on]DJ > Houghton---10/26/2011 09:56:25 AM---The file is most likely updated when the > reconciler is run on startup. What are you changing in the **** > > > From:**** > > > DJ Houghton/Ottawa/IBM@IBMCA**** > > > To:**** > > > P2 developer discussions <[email protected]>**** > > > Date:**** > > > 10/26/2011 09:56 AM**** > > > Subject:**** > > > Re: [p2-dev] Is there a way to update the file config.ini?**** > > > Sent by:**** > > > [email protected]**** > ------------------------------ > > > > > The file is most likely updated when the reconciler is run on startup. What > are you changing in the config.ini? There are touchpoint actions for > adding/removing/changing properties. Perhaps a better plan would be to use > the current touchpoint actions (or write a new one) which would modify the > file. We don't encourage (and therefore don't provide means for) clients to > replace the whole file because in general this is a bad idea as it doesn't > allow everyone to place nice with each other. > > > > [image: Inactive hide details for Samuel Wu---2011/10/25 05:09:27 > PM---Hello everyone, We've shipped a config,ini in the product. Now w]Samuel > Wu---2011/10/25 05:09:27 PM---Hello everyone, We've shipped a config,ini in > the product. Now we want to ship a change to **** > > > From:**** > > > Samuel Wu/Toronto/IBM@IBMCA**** > > > To:**** > > > P2 developer discussions <[email protected]>**** > > > Date:**** > > > 2011/10/25 05:09 PM**** > > > Subject:**** > > > [p2-dev] Is there a way to update the file config.ini?**** > > > Sent by:**** > > > [email protected]**** > ------------------------------ > > > > > Hello everyone, > > We've shipped a config,ini in the product. Now we want to ship a change to > it. We have a touch point action which moves the new file to the > configuration directory during the installation of the new feature. But > Eclipse overrides the file with its own version during the restart. Wonder > how to update the config.ini file during the feature update. Thanks. > > Best Regards > > Samuel Wu_______________________________________________ > p2-dev mailing list > [email protected]* > *https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected]* > *https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected]* > *https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > **** > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource
<<image003.png>>
<<image001.gif>>
<<image004.png>>
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
