[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [p2-dev] FW: P2 Profile Questions
|
Hi John,
Yup that's exactly what I was doing. And then from
what you describe I manually fixed up the profile that got generated from
installing the feature directly so that it had the relevant tooling.*
fragments.
So can I create my own product root? This sounds like
what I need to do. Or do I have to use one of the existing
ones?
Cheers
_Paul
Hi Paul, What root IU did you try to install using the director?
If you are missing the fragments (tooling.*), it sounds like you are trying to
install a feature or bundle directly, rather than a proper product root (such as
org.eclipse.sdk.ide or org.eclipse.platform.ide). It is these product roots that
tie the generic feature/bundle IUs together with the configuration data in the
fragments (tooling.* IUs). John
Warren_Paul@xxxxxxx
Sent by:
p2-dev-bounces@xxxxxxxxxxx
11/21/2008 12:47 PM
|
Please respond
to
P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
|
To
| <p2-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [p2-dev] FW: P2 Profile
Questions |
|
Thanks for the responses everyone.
Today I tried to
generate a P2 profile using the director application,
as suggested. It
generated me profile and this looked to be identical
to the one I got when I
used the admin UI. I assume the same underlying
bundles are used here
so no real surprise. At least using the director
means I can automate
the process which is good.
However, this generated profile is still
missing all the tooling.*
bundles and feature IUs and therefore in my
[limited] experience to date
means p2 will fail to provision anything further
(actually I should
caveat that - it wont provision bundles in dropins).
After stepping
through the code I discovered that something in my
profile had to
require the tooling.* IUs otherwise when the provisioning plan
is
created new bundles don't get attached to an installable unit
fragment
which in turn means the engine operands are missing the
parameterized
provisioning action (they only get the pre & post install
actions) which
all ultimately means the new bundles don't get
installed.
Now, bare in mind I am attacking this with little to no prior
knowledge
of p2 so I've just done the best I can by experimenting and
stepping
through the code. Apologies in advance if I have done
something really
stupid. But I am assuming that I have done something
wrong so all help
gratefully recieved? Happy to experiment further if
anyone has any
suggestions.
Many thanks
_Paul
-----Original
Message-----
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Alessandro
Mottadelli
Sent: 21 November 2008 12:52
To: P2 developer
discussions
Subject: Re: [p2-dev] FW: P2 Profile Questions
Pascal
Rapicault ha scritto:
>
> The overall idea of creating what you need
(metadata and profile) as
> part of the build is good and I believe this
is the path to follow.
> What I like about this is that by the same token
that the eclipse you
> download today result from a provisioning
operation, you can then see
> the WAR you ship resulting itself from a
provisioning operation and it
> makes things consistent.
> I
think that what made this whole experience weird for you is
>
deficiencies in our tooling / metadata generation tooling that is
> still
very driven of complete products in a standard eclipse shape.
> This is
something that is being improved as we speak and we are
> looking at ways
to generate metadata from source information and not
> require the
product or whatever you build to be in its final shape.
> We are mostly
focused on RCP product builds, so please make sure to
> follow what is
going there to make sure your scenario is addressed if
>
possible.
>
> One last thing, please try to not use the "dropins"
folder to
> provision... this is the worst way. Try invoking the director
> directly, this will be much cleaner.
>
>
PaScaL
>
Maybe you could publish a p2 metadata spec
?
Maybe the people could generate the metadata they need by themselves
if
they feel that the standard tooling is not what they
need?
_______________________________________________
p2-dev
mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev
mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
