Eclipse Community Forums: Equinox » P2 and default metadata in eclipse/configuration folder in Eclipse releases

Help

Home

Home » Eclipse Projects » Equinox » P2 and default metadata in eclipse/configuration folder in Eclipse releases

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

P2 and default metadata in eclipse/configuration folder in Eclipse releases [message #112476]

Tue, 24 June 2008 21:33

Mark Melvin

Messages: 118
Registered: July 2009

Senior Member

Hi There,

We have hit another P2-related stumbling block with our product installer
interacting with P2 and I just wanted to raise a question. Previous
releases of Eclipse only used to contain a single file in the
"configuration area" of eclipse (the eclipse/configuration folder) - the
"config.ini" file. In the current releases of Eclipse I now see that
there are a few more files, in particular:

eclipse/configuration/.settings/org.eclipse.equinox.p2.artif act.repository.prefs
eclipse/configuration/.settings/org.eclipse.equinox.p2.metad ata.repository.prefs
eclipse/configuration/org.eclipse.equinox.simpleconfigurator /bundles.info
eclipse/configuration/org.eclipse.update/platform.xml

I know in the past at least platform.xml was a generated file, and it
seems to me that the other files in there are also files that are
constantly updated by the P2 engine and reflect a certain system state. I
guess my question is - do they belong in the release zipfile if they are
generated/dynamic metadata? Our installer in "update mode" just killed a
couple of these (they never used to be there!) which basically hoses the
installed platform (i.e. it won't even start anymore).

So I guess I need to update our installer to avoid certain things in this
directory (or the entire directory), but it seems like a good idea to me
to not even include them in a release archive if they are indeed
generated/dynamic files specific to the state of the platform at a
particular moment in time.

Thanks,
Mark.

Report message to a moderator

Re: P2 and default metadata in eclipse/configuration folder in Eclipse releases [message #113649 is a reply to message #112476]

Wed, 09 July 2008 03:12

Pascal Rapicault

Messages: 333
Registered: July 2009
Location: Ottawa

Senior Member

None of the files you mention can be generated at runtime. They are part of
the SDK. For example the bundles.info is what tells OSGi which bundles to
run (see it as a super osgi.bundles propery). As for the two preferences
file you could probably can them but this would depend on what you want your
users to have as pre-defined sites.

"Mark Melvin" <mark.melvin@onsemi.com> wrote in message
news:op.uc9vihw3nuze1b@n-mmelvin.pc.amis.com...
> Hi There,
>
> We have hit another P2-related stumbling block with our product installer
> interacting with P2 and I just wanted to raise a question. Previous
> releases of Eclipse only used to contain a single file in the
> "configuration area" of eclipse (the eclipse/configuration folder) - the
> "config.ini" file. In the current releases of Eclipse I now see that
> there are a few more files, in particular:
>
> eclipse/configuration/.settings/org.eclipse.equinox.p2.artif act.repository.prefs
> eclipse/configuration/.settings/org.eclipse.equinox.p2.metad ata.repository.prefs
> eclipse/configuration/org.eclipse.equinox.simpleconfigurator /bundles.info
> eclipse/configuration/org.eclipse.update/platform.xml
>
> I know in the past at least platform.xml was a generated file, and it
> seems to me that the other files in there are also files that are
> constantly updated by the P2 engine and reflect a certain system state. I
> guess my question is - do they belong in the release zipfile if they are
> generated/dynamic metadata? Our installer in "update mode" just killed a
> couple of these (they never used to be there!) which basically hoses the
> installed platform (i.e. it won't even start anymore).
>
> So I guess I need to update our installer to avoid certain things in this
> directory (or the entire directory), but it seems like a good idea to me
> to not even include them in a release archive if they are indeed
> generated/dynamic files specific to the state of the platform at a
> particular moment in time.
>
> Thanks,
> Mark.

Report message to a moderator

Previous Topic:	Equinox porting
Next Topic:	[p2] Updating while keeping constraints satisfied

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 19:53:31 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter