On 28 Oct 2010, at 12:29, Justin Edelson wrote: > I don't think that's happened yet. What might be happening is that the > bundles aren't reloaded unless the timestamp of the launchpad base JAR has > changed.
Checked that, Recreated the jar, and the bundle jars inside with all the timestamps after everything in the sling folder. No update happens. Its not that much a problem we manage our servers with puppetd, and we can change the upgrade mechanism to loading over http or one of the felix mechanisms. (eg filesystem). The production team here don't like the idea of putting the jars in the JCR, so we probably wont use that one. > > Ian- try running a debugger and you should be able to see where in > BootstapInstaller the decision is made to skip installation/upgrade. > > What I had to so is delete the bootstapinstaller.ser file manually. If this > file is missing, bundles will always be installed/upgraded. Ok thats a good workaround and a safe switch, and upgrades just the new ones as before. If possible it would be really helpful to keep that "feature" Thanks Ian > > Justin > > On Oct 28, 2010, at 5:57 AM, Felix Meschberger <[email protected]> wrote: > >> Hi, >> >> IIRC we just discussed to remove this functionality from the launchpad >> and replace it with an extension to the OSGi Installer. >> >> But I do not exactly know where are standing here .... Maybe Carsten >> and/or Justin know more. >> >> Regards >> Felix >> >> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: >>> Hi, >>> >>> I might have missed a change in the launchpad/bootloader >>> >>> When re rebuild the standalone jar with additional bundles or updatede >>> bundles and restart and existing Sling instance, the new or updated bundles >>> are not updated. The only way to update jars appears to be via one of the >>> other methods (web console, file install, jcr installer). >>> >>> Was there a change to the launchpad ? >>> I am sure this used to work. >>> Ian >>> >> >>
