Hi John, Yes I modified the contents of the launchpad/base module yesterday thereby removing the Servlet API and the OSGi Http Service API from the launcher and thus from the System Bundle exports.
Unfortunately this was not complete as the standalone application still registered the Servlet API packages as system bundle exports. This is now fixed and it should work again. Sorry for the inconvenience. Regards Felix John Crawford schrieb: > Hello, > > Yesterday evening I tried to checkout Sling from source (trunk) and run the > standalone application. The build went okay (as long as I suppressed the > tests), however, when it came time to run the framework, it acted like it > was starting up, but failed immediately. There were no error messages and > no debug messages that I could find to explain why (at least to the console > with the -f - option). This morning I saw a change to the standalone > launcher [1] and wanted to ask if this was the fix for what I was > experiencing last night? > > I am also assuming the procedure hasn't changed since the posting of this > documentation [2] (Build Sling - With the maven command line). In the > meantime, I went ahead and used the build [3] from May 2009(?). > > Respectfully, > John > > [1] > SLING-1179 Servlet API is not available in the launcher any more, thus we > have to remove the system package declaration in the standalone application > > [2] > http://sling.apache.org/site/getting-and-building-sling.html > > [3] > http://sling.apache.org/site/downloads.html >
