Hi, On Sat, Jan 3, 2009 at 7:09 AM, Torgeir Veimo <[email protected]> wrote: > ...If I take the current sling svn trunk code, do a mvn install in the root, > then a mvn install in launchpad/webapp, then use the resulting war file in > the target directory, then I should get the latest sling trunk code?...
Yes, but the launchpad app and webapp modules do not necessarily use snapshot versions of all bundles, some dependencies are still on the released versions of bundles. > ...The simple webdav servlet configuration only has options for the > authentication realm and the root path. Am a bit at a loss here..... The launchpad/webapp was using the 2.0.2.incubator version of the org.apache.sling.jcr.webdav bundle, as can be verified by looking at the bundle details from the OSGi console. I have fixed this in the launchpad/app module, which is used to build launchpad/webapp. Rebuilding revision 730968 as you did should now get you the webdav bundle from trunk. Note that you could also have updated the org.apache.sling.jcr.webdav bundle manually after starting the launchpad webapp, for example by building the webapp bundle using mvn -P autoInstallBundle clean install -D sling.url=http://localhost:8888/system/console The bundles that are embedded in the war file are only used for the initial installation, but if you update them manually after startup the updated versions are permantently stored in the sling.home folder. -Bertrand
