Hi Andreas, all with http://svn.apache.org/r1533921 the trunk now uses version 2.2.1. Created STANBOL-1182 for this task
best Rupert On Sun, Oct 20, 2013 at 2:17 PM, Rupert Westenthaler <rupert.westentha...@gmail.com> wrote: > Hi Andreas, > > Issues like that are the hardest to find ... > > The old jetty version is a dependency of > > org.apache.felix: org.apache.felix.http.jetty:2.2.0 > > that was released on "26-Jan-2011". After checking I have seen that > with "18-Sep-2013" version 2.2.1 got release. This version depends on > newest stable Jetty version "8.1.13.v20130916". I will upgrade the > dependency. Lets see maybe this solves your issue. > > Will give you a ping as soon I have done the upgrade and tested the new > version > > best > Rupert > > > On Sun, Oct 20, 2013 at 11:26 AM, Andreas Kuckartz <a.kucka...@ping.de> wrote: >> Andreas Kuckartz: >>> When I execute >>> $ mvn -o clean install -DkeepJarRunning=true -Dhttp.port=5679 >>> >>> in the integration-tests directory I see these lines (context below): >>> >>> [INFO] Detected extended HttpService. Filters enabled. >>> [INFO] Started jetty 6.1.x at port(s) HTTP:5679 >>> [INFO] Detected extended HttpService. Filters enabled. >>> [INFO] Started jetty 6.1.x at port(s) HTTP:5679 >>> >>> Any idea why the two lines are output twice? >> >> That does not seem to be a completely new problem: >> >> http://apache-sling.73963.n3.nabble.com/Sling-sometimes-return-404-on-all-requests-after-startup-td1992032.html >> >> Another question: >> Jetty 6.1 seems to be quite old, more precisely: deprecated. >> >> Is there a reason not to use a newer version? >> >> Cheers, >> Andreas > > > > -- > | Rupert Westenthaler rupert.westentha...@gmail.com > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen