Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseCon 2010 p2 tutorial

Revision as of 15:44, 14 January 2010 by Unnamed Poltroon (Talk)

Build specific suggestions

  • Product based builds with p2
  • Using repository tools such as the slicer, repo2runnable and mirror to build smaller components from existing repositories
  • process.p2.repo
  • comparator
  • remove.iu
  • Building composite repositories
  • Repository management
  • Using the publisher
  • Assembling product out of pre-existing components (no compiling)
  • Overview of pde build process to create metadata for product builds
    • setting start levels
    • specifying launchers
    • configuration properties


P2 focus

  • p2 for RCP developers (everything you need to know to make use of p2 in RCP -- including at build + packaging time, at run-time, to provide self updating apps, etc...).
  • self updating - headless and non-headless. See also the RCP update long talk . I am thinking something along the lines of Equinox/p2/Adding Self-Update to an RCP Application (which will be updated before EclipseCon to cover the current state of the world). It would be really helpful to include adding self-update support as part of a sequence:
    • build your first app and include self-update support
    • add a new feature to your app, rebuild it, put it in the repo and show the self-update working
  • Something similar for OSGi developers. (Obviously things are very similar, but we would have to pick an example and focus on it during the tutorial).


Grumpy has left a new comment on your post "p2 tutorial RFC":

I'd really like to see someone explore using P2 for mass (as in pushing/pulling bundles to around 180 global branches) deployment scenarios. It seems to me there would be lots of tooling above and beyond P2 to handle. It would be nice to have someone explore various paths. Another challenging area is the intersection of bundle distribution and role based access (governing who can get what bundles).

kmoir> This seems similar to what Sonatype's Nexus talk is discussing.

Back to the top