I would use the UI provided by org.eclipse.equinox.p2.ui. Is this going to be a self-provisioning setup?
In terms of a minimal repository, p2 does not itself define the site layout. This is abstracted out, so you can get as simple as you like. If you want something more minimal than the old update site or a p2 update site then just implement your own repository factory. Extend the org.eclipse.equinox.p2.metadata.repository.metadataRepositories and org.eclipse.equinox.p2.metadata.repository.artifactRepositories. You will need a file at the URL that identifies this as your minimal repository (replacing the site.xml used by the old update manager), and you specify this file as the filter suffix in the extension. Nigel > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:equinox-dev- > [EMAIL PROTECTED] On Behalf Of Matthias Luebken > Sent: Monday, April 14, 2008 12:44 PM > To: equinox-dev@eclipse.org > Subject: [equinox-dev] Small RCP example with p2 > > Hi > > I'm trying to put together a small p2 example: An RCP-App that > triggers an update action and updates a plugin from an update site. > My first question: Is there something like > "UpdateManagerUI.openInstaller()" for p2? > My second: How would a minimal p2-update site look like? > > Thanks in advance. > Matthias > > -- > blog: luebken.com > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
