The installer doesn't really do anything
very interesting. It really just creates a shell, prompts for install location,
and then invokes IDirector.provision to perform the actual install. We
never thought of the installer as the foundation for a commercial quality
installer and thus didn't design much extensibility into it. It does have
some minimal provisional API (package org.eclipse.equinox.internal.provisional.p2.installer),
which I could imagine promoting to real API in 3.5. I suspect this still
won't be sufficient for your needs and you would be better off writing
your own installer that just invokes the IDirector API to perform the actual
Pedro Carneiro <pjsc@xxxxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
06/12/2008 11:22 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
As far as I understood, the given installer is an example given by Eclipse
of how we can create an installer based on equinox (p2) and does not have
extension points available (right now). Is that right?
The essence of my question is because I would like to create an installer
top of p2 and add some functionalities to it. As all eclipse-based products
are distributed over the EPL license, I would like to know if have a way
contribute with new functionalities to it without modifying the given
example code, that is, using its available extension points.
Pascal Rapicault wrote:
> If you are talking about the installer as available at
> taking it apart / modifying / extending it is expected. This installer
> application has more the goal of being an exemplary application than
> something to be reused directly out of the box even though it could.
> In the long run, with everyone writing their own standalone installer
> p2, I hope we can gather all this code and create a common base, or
> have a pool of reusable components to share.
> From: Pedro Carneiro <pjsc@xxxxxxxxxxxx>
> To: equinox-dev@xxxxxxxxxxx
> Date: 06/12/2008 07:35 AM
> Subject: [equinox-dev] p2 installer provides extension
> Hi all,
> I would like to know if p2 installer provide extension points. If
> are them?
> I'm asking this because in all the discussions that I read before
> developers are modifying the native installer behavior. Is this the
> way to do this?
> I did not find a lot of documentation about the new p2 equinox installer
> functionality (the great part comes from the eclipse wiki) and the
> does not talks about this.
> Reading suggestions are always welcome.
> View this message in context:
> Sent from the Equinox - Dev mailing list archive at Nabble.com.
> equinox-dev mailing list
> equinox-dev mailing list
View this message in context: http://www.nabble.com/p2-installer-provides-extension-points--tp17737477p17802640.html
Sent from the Equinox - Dev mailing list archive at Nabble.com.
equinox-dev mailing list