Hi, Torgeir Veimo schrieb: > > On 3 Jan 2009, at 20:35, Bertrand Delacretaz wrote: > >> Hi, >> >> On Sat, Jan 3, 2009 at 7:09 AM, Torgeir Veimo <torg...@pobox.com> 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. >>> > > Ok, so launchpad != latest trunk.
Hmm, I would consider this a "bug", then. Thanks, Bertrand for fixing this. > What is the easiest way to run the > latest modules? Launchpad should really get you the latest modules - unless launchpad is not updated for the latest modules. In this case it was mea culpa, sorry. > >> 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 > > > Thank you! running this command in jcr/webdav fixed my problem! > Great ! Good to hear. Regards Felix
