|
| Re: Software update [message #54787 is a reply to message #54469] |
Mon, 12 December 2005 23:18   |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
the update can go pretty deep. The Eclipse Update Manager for example
allows you to lay down new versions of any bundle (including the framework
itself). In some cases the updates could be activated dynamicially (without
restarting). However, in general, the bundle being updated needs to be
first stopped, then updated, the restarted. When you update the bundle, any
bundles that depend on it must also be stopped and started.
So you see that, for exapml,e updating the runtime bundle would likely shut
down all/most of Eclipse. Note also that it requires all the bundles
involved to be clean (unregister listeners etc).
You can also update the so-called "root files" (eclipse.exe, config.ini,
startup.jar) if you use install handlers.
Jeff
"Stefan Liebig" <Stefan.Liebig@compeople.de> wrote in message
news:7e4625f46c3802a20f1249df62e21e87$1@www.eclipse.org...
> OSGi platforms (Equinox) should be a good platform for dealing with
> software
> updates. Some service could look for updates (automaticaly/"manualy"
> triggered),
> download them and then replace the outdated bundle.
>
> My question is: How "deep" can the software update work? Are their
> possibilites
> that the software update service can also update itself or the complete
> platform
> without restarting the JVM?
>
>
|
|
|
| Re: Software update [message #54974 is a reply to message #54787] |
Thu, 15 December 2005 13:51 |
 Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Sounds pretty good. But how does the magic work that code which is
currently running (update service?) replaces itself (file locks,..)?
Jeff McAffer wrote:
> the update can go pretty deep. The Eclipse Update Manager for example
> allows you to lay down new versions of any bundle (including the framework
> itself). In some cases the updates could be activated dynamicially (without
> restarting). However, in general, the bundle being updated needs to be
> first stopped, then updated, the restarted. When you update the bundle, any
> bundles that depend on it must also be stopped and started.
>
> So you see that, for exapml,e updating the runtime bundle would likely shut
> down all/most of Eclipse. Note also that it requires all the bundles
> involved to be clean (unregister listeners etc).
>
> You can also update the so-called "root files" (eclipse.exe, config.ini,
> startup.jar) if you use install handlers.
>
> Jeff
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> wrote in message
> news:7e4625f46c3802a20f1249df62e21e87$1@www.eclipse.org...
>
>>OSGi platforms (Equinox) should be a good platform for dealing with
>>software
>>updates. Some service could look for updates (automaticaly/"manualy"
>>triggered),
>>download them and then replace the outdated bundle.
>>
>>My question is: How "deep" can the software update work? Are their
>>possibilites
>>that the software update service can also update itself or the complete
>>platform
>>without restarting the JVM?
>>
>>
>
>
>
|
|
|
|
| Re: Software update [message #57588 is a reply to message #54974] |
Tue, 24 January 2006 04:00 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Updating bundles is ok since you are actually laying down a completetly new
JAR beside the old one. Then you either restart the framework or recycle
the bundle.
Updating the root files is more complicated. Right now updating things like
eclipse.exe and startup.jar is harder because they are shared and typically
locked and do not have version numbers. We have been talking about a)
making stratup.jar into a versioned file (perhaps in the plugins dir) and b)
a way of updating eclipse.exe by putting a copy beside the old one and then
swapping on restart.
Jeff
"Stefan Liebig" <Stefan.Liebig@compeople.de> wrote in message
news:dnrsdu$p3q$1@news.eclipse.org...
> Sounds pretty good. But how does the magic work that code which is
> currently running (update service?) replaces itself (file locks,..)?
>
> Jeff McAffer wrote:
> > the update can go pretty deep. The Eclipse Update Manager for example
> > allows you to lay down new versions of any bundle (including the
framework
> > itself). In some cases the updates could be activated dynamicially
(without
> > restarting). However, in general, the bundle being updated needs to be
> > first stopped, then updated, the restarted. When you update the bundle,
any
> > bundles that depend on it must also be stopped and started.
> >
> > So you see that, for exapml,e updating the runtime bundle would likely
shut
> > down all/most of Eclipse. Note also that it requires all the bundles
> > involved to be clean (unregister listeners etc).
> >
> > You can also update the so-called "root files" (eclipse.exe, config.ini,
> > startup.jar) if you use install handlers.
> >
> > Jeff
> >
> > "Stefan Liebig" <Stefan.Liebig@compeople.de> wrote in message
> > news:7e4625f46c3802a20f1249df62e21e87$1@www.eclipse.org...
> >
> >>OSGi platforms (Equinox) should be a good platform for dealing with
> >>software
> >>updates. Some service could look for updates (automaticaly/"manualy"
> >>triggered),
> >>download them and then replace the outdated bundle.
> >>
> >>My question is: How "deep" can the software update work? Are their
> >>possibilites
> >>that the software update service can also update itself or the complete
> >>platform
> >>without restarting the JVM?
> >>
> >>
> >
> >
> >
|
|
|
Powered by
FUDForum. Page generated in 0.03394 seconds
] 
Search
Help
Register
Login
Home
