Classic Update instead of P2 for RCP app [message #114456] |
Fri, 18 July 2008 09:26  |
Eclipse User |
|
|
|
Originally posted by: klammer.utanet.at
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
|
|
|
|
|
|
Re: Classic Update instead of P2 for RCP app [message #483583 is a reply to message #114494] |
Wed, 02 September 2009 04:45  |
Eclipse User |
|
|
|
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@ca.ibm.com> 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@utanet.at> wrote in message
> news:g5q5lq$oi3$1@build.eclipse.org...
>> 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.
|
|
|
Powered by
FUDForum. Page generated in 0.03503 seconds