Re: No success trying Sling
Hi Andreas, we are very sorry about the current situation - thanks for reporting the problems! We're currently working on fixing the download page and it should be working again very soon. If during a build tests are failing, the easiest thing to get a running Sling at the end, is to disable the tests by running mvn -Dmaven.test.skip=true install It's not the way it should be, but nevertheless gets you the wanted result :) We're currently working on getting the tests running again. So this is just a temporary problem. In addition we're very hard working on getting the next big milestone, SLING-6, ready - this will be a ready to start download of the latest and greatest :) We're currently in the middle of the process, so SLING-6 should be ready in some weeks. If you have additional comments or run into other problems, please let us know. Regards Carsten Andreas Kuckartz wrote Hello! yesterday I wanted to try Sling again and have a look at David Mini CMS https://cwiki.apache.org/SLING/gsoc-2010-mini-cms-project.html Unexpectedly that failed (not because of David Mini CMS). First I found out that no binaries are available on the website because the links are broken: https://issues.apache.org/jira/browse/SLING-1768 (The download page states: Note that the above releases are relatively old (May 2009). If you want to experiment with bleeding edge code, building Sling yourself is not that hard.. Why are no binaries of the most recent released version made available?!) Then I spent some time finding an old file for sling in the archive and tried to install David Mini CMS on it. But that also failed because some of the dependencies are not met. Obviously and understandably David Mini CMS depends on more recent Sling components than those provided by an obsolete version of Sling. Then I tried to build Sling from the sources with Maven according to http://sling.apache.org/site/getting-and-building-sling.html But that also failed because testSemiRandomInstall fails: https://issues.apache.org/jira/browse/SLING-1737 And at the end launching Sling of cause also fails because there is no jar file to be launched. Cheers, Andreas -- Carsten Ziegeler cziege...@apache.org
David Mini CMS core (core) does not start (Re: No success trying Sling)
Thanks, Carsten, for your informative reply and hint! I am now running a freshly built Sling. But David Mini CMS still has problems. The bundle David Mini CMS core (core) does not start: ERROR: org.apache.sling.commons.scheduler,version=2.1 -- Cannot be resolved I have also appended the log. I did not find org.apache.sling.commons.scheduler in the list of bundles displayed in the Apache Sling Web Console. Cheers, Andreas --- 14.09.2010 10:08:21.692 *ERROR* [1704184...@qtp-1616586953-8] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0))) org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1709) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892) at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:428) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:375) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:77) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Hi Andreas, you need that bundle installed to start David. You can find it in http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/scheduler/ http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/scheduler/Once you created the bundle, you can install it using the console. Bye, Federico 2010/9/14 Andreas Kuckartz a.kucka...@ping.de Thanks, Carsten, for your informative reply and hint! I am now running a freshly built Sling. But David Mini CMS still has problems. The bundle David Mini CMS core (core) does not start: ERROR: org.apache.sling.commons.scheduler,version=2.1 -- Cannot be resolved I have also appended the log. I did not find org.apache.sling.commons.scheduler in the list of bundles displayed in the Apache Sling Web Console. Cheers, Andreas --- 14.09.2010 10:08:21.692 *ERROR* [1704184...@qtp-1616586953-8] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0))) org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1709) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892) at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:428) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:375) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:77) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Cheers, Andreas
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Andreas Kuckartz wrote I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Maybe we should add those to the launchpad by default? Carsten -- Carsten Ziegeler cziege...@apache.org
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
On Tue, Sep 14, 2010 at 10:42 AM, Carsten Ziegeler cziege...@apache.org wrote: Andreas Kuckartz wrote I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Maybe we should add those to the launchpad by default? +1, those are commonly used. -Bertrand
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Now the first real problem with David Mini CMS: I want to save the first new page but an error message Error during save pops up and the log contains this entry: 14.09.2010 10:58:22.121 *ERROR* [127.0.0.1 [1284454702109] POST /content/david/2010/09/15/ HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Access Denied Access denied. I am logged in as admin. Cheers, Andreas
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
That problem disappeared with the latest Sling revision. Cheers, Andreas Am 14.09.2010 11:02, schrieb Andreas Kuckartz: Now the first real problem with David Mini CMS: I want to save the first new page but an error message Error during save pops up and the log contains this entry: 14.09.2010 10:58:22.121 *ERROR* [127.0.0.1 [1284454702109] POST /content/david/2010/09/15/ HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Access Denied Access denied. I am logged in as admin. Cheers, Andreas
