Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Migrating Update Manager to Eclipse 3.4 p2 provisioning
Migrating Update Manager to Eclipse 3.4 p2 provisioning [message #111822] Thu, 12 June 2008 16:37 Go to next message
Eclipse User
Originally posted by: cendle.spss.com

Hi,

We have an RCP application that is currently on Eclipse 3.3. It is using
the existing Update Manager to update its features/plug-ins. We are
moving to Eclipse 3.4 and are thinking of using the new p2 provisioning.

Is p2 going to be stable and is it advisable to move to p2 or should we
wait for another Eclipse release before migrating? I have seen some
comments/blogs indicating there is still a lot of work to get done
regarding p2.

If we do use p2, we will need to migrate our Eclipse RCP install and the
Update Manager to p2.

Is there any detailed information on how to use the new p2 APIs? Where
are the APIs located?

How should we migrate from using Update Manager to using p2? Are there
tools to help?

I have seen several Eclipse wiki pages but most of them are high level
and describe how to use p2 from within Eclipse, not how to develop using
p2. Does anyone know of any good wikis that have a good explanation of
how developers can use p2?

Thanks in advance,
Cory
Re: Migrating Update Manager to Eclipse 3.4 p2 provisioning [message #111991 is a reply to message #111822] Thu, 12 June 2008 22:18 Go to previous message
Pascal Rapicault is currently offline Pascal Rapicault
Messages: 283
Registered: July 2009
Location: Ottawa
Senior Member
"Cory" <cendle@spss.com> wrote in message
news:g2s1e5$j01$1@build.eclipse.org...
> Hi,
>
> We have an RCP application that is currently on Eclipse 3.3. It is using
> the existing Update Manager to update its features/plug-ins. We are moving
> to Eclipse 3.4 and are thinking of using the new p2 provisioning.
>
> Is p2 going to be stable and is it advisable to move to p2 or should we
> wait for another Eclipse release before migrating? I have seen some
> comments/blogs indicating there is still a lot of work to get done
> regarding p2.
Do you think that if it was not stable enough the Eclipse PMC would have
let it in the SDK?
You should know that you can't trust everything you read on the internet
:)
More seriously we have had a lot of users and have addressed all the
critical bugs. It is not to say that there are not things that can be
improved. However the team is confident with the state of affair when it
comes to install plugins, features, configure config.ini, eclipse.ini and
such. So if you are only doing those I would not wait.

> If we do use p2, we will need to migrate our Eclipse RCP install and the
> Update Manager to p2.
>
> Is there any detailed information on how to use the new p2 APIs? Where are
> the APIs located?
This is one point that we have decided to defer until 3.5 because we
were not confident to make API something that had no user. However we still
had a pretty good idea of what we wanted in that space, therefore we made
all things we want to eventually become API available in packages named
"provisional", this way people can start using it and providing feedback.

> How should we migrate from using Update Manager to using p2? Are there
> tools to help?
There is a little bit of information in the Help, however it is not
great. We will try to put some doc together, but for now asking question
here is probably what is best. Also the guidance could depend on where you
start from and what you are trying to do.


> I have seen several Eclipse wiki pages but most of them are high level and
> describe how to use p2 from within Eclipse, not how to develop using p2.
> Does anyone know of any good wikis that have a good explanation of how
> developers can use p2?
The point of 1.0 was to make it relatively transparent to plug-in and
feature authors (they should have nothing to do). Of course if you are
developing an RCP app, then you may be impacted a bit more since you would
have to create p2 metadata for your install but again this should not be a
concern of everyone in the team, mostly of the release engineer type of
person.

Don't hesitate to contact us in this newsgroup with more questions.

Thx for your inquity,

PaScaL

>
> Thanks in advance,
> Cory
Previous Topic:Re: How to Commit a document
Next Topic:missing constraint import package sun.rmi.registry
Goto Forum:
  


Current Time: Tue Jul 22 17:43:57 EDT 2014

Powered by FUDForum. Page generated in 0.02157 seconds