OK, fair question :-) The reason we decided to do this was on far more prosaic level, although I hope that someone will comment on your question regarding OSGi capabilities. In some cases, update of an IPS package would involve removal of the existing file (either the file got removed from the distribution, or it has moved into a different directory, or it has been renamed). If such a file was in use during the update, update would fail on Windows platform due to Windows file lock mechanism. Given that providing different Admin GUI implementation based on OS was not particularly good option either, we decided to make the Admin GUI update functionality "read only" across the platforms and defer updates/package uninstallations to pkg and updatetool. In the future releases we should be able to get this to work by forcing the server restart in order to update the files, Windows update style, but it was too late for that in this release.

Back to OSGi - I believe that Alexis played with upgrade quite a lot and in some instances he reportedly had to clean up OSGi cache directory before being able to restart the server which may mean that things are not yet completely seamless on OSGi update level either.

Thanks,

Snjezana

Wouter van Reeven wrote: