FYI - I could reproduce the issue only by deploying the jar via webconsole and not performing a package refresh. If I either deploy the bundle via the installer itself or manually trigger refresh packages the installer works quite fine.
Cheers Dominik On Fri, Feb 17, 2017 at 9:59 AM, Dominik Süß <[email protected]> wrote: > Hi Dan, > > can you crosscheck if the same happens for a previous version of Sling > Installer to be deployed (e.g. installing 3.8.2 when an older version was > deployed before). I can't see any chance that this fix introduces new > issues into restart behavior of bundle and therefore would opt to move on > and open a new issue for the found restart condition. > > +1 nonbinding > > Cheers > Dominik > > On Fri, Feb 17, 2017 at 6:00 AM, Daniel Klco <[email protected]> wrote: > >> Hi Karl, >> >> I was checking the integration tests and noticed that >> org.apache.sling.installer.core 3.8.4 cannot be installed into a running >> Sling instance. Once you restart the instance it's fine, but when you >> first >> install the bundle, it causes a number of other bundles to fail. Is this a >> known problem? >> >> Please find logs from Sling & the failed integration tests below: >> >> https://gist.github.com/klcodanr/4984b27cb54719ce069d6347b4298647 >> >> Thanks, >> Dan >> >> On Thu, Feb 16, 2017 at 10:27 AM, Robert Munteanu <[email protected]> >> wrote: >> >> > On Thu, 2017-02-16 at 16:21 +0100, Karl Pauls wrote: >> > > Please vote to approve this release: >> > >> > +1 >> > >> > Robert >> > >
