Eclipse Community Forums: Buckminster » custom default start level or contig.ini

Help

Home

Home » Archived » Buckminster » custom default start level or contig.ini

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

custom default start level or contig.ini [message #490957]

Mon, 12 October 2009 15:13

Alex Chatziparaskewas

Messages: 52
Registered: July 2009

Member

Hi

Using buckminster to create an update site and the p2 director for subsequent installation of a feature based product: Is there any way that would allow me configuring a different default start level (osgi.bundles.defaultStartLevel) other than 4?? Alternatively, can I somehow specify my completely own config.ini?

Everything I tried so far did not work (in particular ticking 'own' config ini in the product definition), the last thing I can think of is writing my own touchpoint allowing installation my complete customized ...

Thanks & Regards
Alex

Report message to a moderator

Re: custom default start level or contig.ini [message #490979 is a reply to message #490957]

Mon, 12 October 2009 15:59

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Hi Alex,
Start levels should be configured using the product definition file. The publisher should pick that up and propagate it
correctly to the p2 repository.

Regards,
Thomas Hallgren

On 10/12/2009 05:13 PM, Alex Chatziparaskewas wrote:
> Hi
>
> Using buckminster to create an update site and the p2 director for
> subsequent installation of a feature based product: Is there any way
> that would allow me configuring a different default start level
> (osgi.bundles.defaultStartLevel) other than 4?? Alternatively, can I
> somehow specify my completely own config.ini?
>
> Everything I tried so far did not work (in particular ticking 'own'
> config ini in the product definition), the last thing I can think of is
> writing my own touchpoint allowing installation my complete customized ...
>
> Thanks & Regards
> Alex

Report message to a moderator

Re: custom default start level or contig.ini [message #491026 is a reply to message #490979]

Mon, 12 October 2009 20:39

Alex Chatziparaskewas

Messages: 52
Registered: July 2009

Member

Hi Thomas

The problem is not the start level of the individual plugins - that is a different issue. The problem is the osgi.bundles.defaultStartLevel, which is always set to 4. The best thing I have found so far in setting this is to set - as part of the product defintion - the property as part of the configurations element:

...
<configurations>
<plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="0" />
<plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="5" />
<plugin id="test.plugin2" autoStart="true" startLevel="4" />
<property name="osgi.bundles.defaultStartLevel" value="6" />
<property name="org.eclipse.update.reconcile" value="false" />
</configurations>
...

However, this did not work.

Regards
Alex

Report message to a moderator

Re: custom default start level or contig.ini [message #491396 is a reply to message #491026]

Wed, 14 October 2009 12:44

Alex Chatziparaskewas

Messages: 52
Registered: July 2009

Member

Hi

Found the solution myself: The solution is to specify the desired default start level as a vmarg. It seems like this takes precedents over the settings generated into the config.ini.

Regards
Alex

PS: Suprisingly, using the approach of the previous post, the desired default start level seems to be reflected in the repository meta data. However, it somehow does not make it into the config.ini. Maybe this is an 'Eclipse' issue.

Report message to a moderator

Previous Topic:	Ant builder in headless mode
Next Topic:	Resolution of svn:externals

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 16:40:09 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter