On Thu, Dec 17, 2009 at 6:15 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > I'm wondering if this operation is supposed to work (tested on > org.apache.sling.launchpad.app-5-incubator and a CRX development > version at work): > > 1. I have org.apache.sling.jcr.resource-2.0.4-incubator.jar installed > and want to upgrade it to the latest version from Sling trunk. > > 2. I use the web console to install 2.0.7-SNAPSHOT, and get dependency > version issues with API and Adapter and Classloader. > > 3. I use the web console to install the latest SNAPSHOT versions of > those dependencies. > > 4. Now the dependency issues are solved, and I can start the Resource > Resolver bundle. > > Unfortunately now all my HTTP requests fail with a 404 error. The > problem gets solved when I do a full restart of Sling. > > Questions: > > * Why did the upgrade break the HTTP requests? I would have expected > that after the upgrade the system should have been back to an > operational state without requiring a restart.
Could this be https://issues.apache.org/jira/browse/SLING-1163? > * Why does the "patch version" upgrade from 2.0.4 to 2.0.7 require > changes in dependencies? I would have expected that a patch version > upgrade would have worked as a drop-in replacement. -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
