Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseCon 2010 p2 tutorial"

Line 19: Line 19:
  
 
*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...).  
 
*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  [https://www.eclipsecon.org/submissions/2010/view_talk.php?id=1205] .  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:
+
*self updating - headless and non-headless.  See also  [https://www.eclipsecon.org/submissions/2010/view_talk.php?id=1205 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
 
** 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
 
** add a new feature to your app, rebuild it, put it in the repo and show the self-update working

Revision as of 09:55, 14 January 2010

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).

Back to the top