I have been reading the code for File Install and it looks like it keeps track of a list of bundles that it is managing in DirectoryWatcher.currentManagedArtifacts (package private). When it encounters an artifact that is not already in that list, it assumes it must be new and installs it. There seems no easy way to prevent this behavior.
I assumed that File Install would not attempt to install bundles that were already running, but thinking more about it, it makes sense that it has to keep track of the list of installed bundles itself. Being a separate bundle it has no intimate knowledge of the Felix bundlecache... -Stijn -----Original Message----- From: Stijn de Witt [mailto:[email protected]] Sent: maandag 7 juni 2010 11:30 To: [email protected] Subject: File Install treats manually installed bundles as new when it starts Hi, As part of our upgrade process, we install our application's bundles manually to prevent File Install from running during the upgrade. Once the upgrade has completed, we start File Install. However, at that point it treats all bundles we already started manually as 'new' and starts uninstalling the old ones and installing the 'new' ones. So basically we see all our bundles being installed again. Does anyone maybe recognize this behavior? Can we prevent it from happening? -Stijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
