[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.equinox] Re: Classic Update instead of P2 for RCP app

We are not shipping the platform feature as is, but several of it's plug-ins.
Since we are having some problems with the classic update system in 3.4,
what platform feature plug-ins could interfere with it's operation?


Thanks for any hints,
Sakis

On Fri, 18 Jul 2008 21:26:26 +0300, Pascal Rapicault <pascal_rapicault@xxxxxxxxxx> wrote:

If you are not shipping the platform feature (org.eclipse.platform), which I
guess you don't since you are building an RCP
then you don't need to do anything particular. Keep on building your RCP
application with org.eclipse.update.core, ui and update.configurator. The
presence of simpleconfigurator will not be harmful.



"Claus Klammer" <klammer@xxxxxxxxx> wrote in message news:g5q5lq$oi3$1@xxxxxxxxxxxxxxxxxxxx
Our product requires support for installing updates. We don't want to
migrate our update process for now. Therefore I would like to know how we
can use Classic Update and get rid of the new P2 Software Update menu
entry. Is this possible at all? Has anyone exported a product with the old
update enabled sucessfully?


Thanks in advance,
Claus Klammer






-- Sakis Kotisis

SciGen Technologies, Inc.