Community
Participate
Working Groups
In order to ensure uniqueness of the IU for a given plug-in, p2 and the SDK, the consumer of ECF bundles, would appreciate if p2 metadata could be generated on every build.
Not sure what's being asked here. Are you saying that you would like us (ECF) to produce p2 metadata as part of our build of the ~10 ECF bundles being contributed to the platform/sdk? If this is what you are asking...then why? My understanding of the way the ECF bundles were being consumed was via an inclusion of the previously-built ECF bundles (i.e. like Orbit bundles are consumed)...not via p2 metadata. In order to keep our own build as simple as possible we would prefer that we don't generate any more than we have to for platform consumption...particularly since we have to also a different set of things for other distributions (e.g. ECF releases).
What I want is fairly straightforward, generate p2 metadata for every build. This is in direct alignment with the MUST DO of Galileo (see bug #254062). Why, so that the SDK can implement what we advocate, reuse of metadata as described in http://wiki.eclipse.org/Equinox/p2/Meetings/20090112 by using the PDE Build / p2 fetch support that got released in M5. Note that we are also planning on changing Orbit (see bug #241427)
(In reply to comment #2) > What I want is fairly straightforward, generate p2 metadata for every build. > This is in direct alignment with the MUST DO of Galileo (see bug #254062). > Why, so that the SDK can implement what we advocate, reuse of metadata as > described in http://wiki.eclipse.org/Equinox/p2/Meetings/20090112 by using the > PDE Build / p2 fetch support that got released in M5. > > Note that we are also planning on changing Orbit (see bug #241427) > ECF will generate metadata for it's own bundles...in fact we are looking forward to it as it will make a better/easier way for ECF to be consumed in pieces...but what we would like to avoid is having to generate special metadata for the platform *and* ECF-distributed features/groups. We've seen that doing things special for the platform can easily become a build/maintenance struggle for us (cf the p2-won't-install-ecf-core-update bundles issue). I suppose this can be accomodated by having one source feature that includes all the platform-required ECF bundles. Unless we can get some releng support though I'm not sure if it can be in place for Galileo.
FWIW p2 metadata generation should merely be a matter of adding generate.p2.metadata=true p2.metadata.repo=file:/path/to/updateSite/staging/location p2.artifact.repo=file:/path/to/updateSite/staging/location http://help.eclipse.org/ganymede/topic/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm
(In reply to comment #4) > FWIW p2 metadata generation should merely be a matter of adding > > generate.p2.metadata=true > p2.metadata.repo=file:/path/to/updateSite/staging/location > p2.artifact.repo=file:/path/to/updateSite/staging/location > > http://help.eclipse.org/ganymede/topic/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm > ok...thanks. But as with anything associated with the build I expect it to eventually be more complicated than this ;-). And Markus...will this create any challenges/issue wrt ECF use of buckminster for build?
(In reply to comment #5) > ok...thanks. But as with anything associated with the build I expect it to > eventually be more complicated than this ;-). Damn you Murphy. ;-) > And Markus...will this create any challenges/issue wrt ECF use of buckminster > for build? Sure it does. BM doesn't support generating p2 meta data (yet). But that build step is currently still done with good old PDE build anyway.
> ECF will generate metadata for it's own bundles...in fact we are looking forward to it as it will make a better/easier way for ECF to be consumed in pieces...but what we would like to avoid is having to generate special metadata for the platform *and* ECF-distributed features/groups. I'm not asking for any special metadata or a favor. I just want the same ECF p2 metadata that you are going to produce for Galileo, produced on a regular basis for us to consume.
ECF's build creates proper p2 repos. Marking as FIXED.
