[news.eclipse.technology.equinox] Re: installer vs director

[Peter Stibrany <peter@xxxxxxxxxx>]

org.eclipse.equinox.p2.exemplarysetup is another one. What are these
plugins good for? Why are they required by director, but not installer?

Peter Stibrany wrote:
> Hello,
> 
> I am trying to find my way through P2. I want to create custom
> 'installer', which will install plugins into target eclipse product.
> User should be able to select his target eclipse product, and my
> 'installer' should be able to check whether plugins are already
> installed and need to be updated, or plugins need to be installed from
> scratch, together with dependencies.
> 
> I am looking at P2 Installer and P2 Director applications to get
> understanding of what I need to do. I am confused by these two sample
> applications though.
> 
> Both seem to work in slightly different way. Biggest noticeable
> difference is set of required P2 plugins they use. P2 Director uses
> "org.eclipse.equinox.frameworkadmin.equinox" and
> "org.eclipse.equinox.simpleconfigurator.manipulator", but P2 Installer
> does not.
> 
> I am able to do the stuff I want via command line using P2 Director, so
> this example application seems to be the best for me to look at.
> 
> What is the purpose of P2 Install then? Why doesn't it need those two
> plugins?
> 
> Thank you for any help.
> 
> -Peter Stibrany