Hi all, sorry but Andreas and myself forgot to add the dev list in the last few mails regarding the integration-test issue of Andreas.
best Rupert ---------- Forwarded message ---------- From: Andreas Kuckartz <a.kucka...@ping.de> Date: Mon, Oct 21, 2013 at 12:00 PM Subject: Re: Jetty version Re: jetty started twice ? To: Rupert Westenthaler <rupert.westentha...@gmail.com> Hi Rupert, bad news: The integration tests in "mvn clean install" still fail. good news: When I start the test launcher and the integration tests sequentially as before they still succeed! I will not have much time today for further tests or investigations. But I really appreciate that you updated the configuration of the relevant components. I have entered an entry in my todo-list to suggest to the Apache Felix team to update the Jetty component. Cheers, Andreas Rupert Westenthaler: > Hi Andres, > > some further investigation revealed: > > * The the jarWebSupport [3] element also supports the <startLevel> > element. So it is possible to change the starlevel of the > felix.http.jetty bundle. > * Checking the imported packages of felix.http.jetty bundle revealed > that it depends on 'felix.configadimg', 'felix.eventadmin' and > 'felix.shell' all started with a level of 5. > > Because of that I suggest to change the level so that > > * the OSGI framework is started at level=2 > * logging is also started at level=2 > * the http.jetty at level=3 and > * the http.whiteboard at level=4 > > This ensures that this infrastructures internal dependencies are > started in the correct order AND that the http services are available > before any other Stanbol bundles are started. > > Those changes are linked to STANBOL-1182 [4] and committed with [5] > > best > Rupert > >> [1] >> http://search.maven.org/#artifactdetails|org.apache.felix|org.apache.felix.http.jetty|2.2.1|jar >> [2] >> http://apache-felix.18485.x6.nabble.com/HTTP-Jetty-implementation-td5004509.html >> [3] >> http://sling.apache.org/site/maven-launchpad-plugin.html#MavenLaunchpadPlugin-ArtifactDefinition > [4] https://issues.apache.org/jira/browse/STANBOL-1182 > [5] http://svn.apache.org/r1534027 > > On Mon, Oct 21, 2013 at 6:37 AM, Rupert Westenthaler > <rupert.westentha...@gmail.com> wrote: >> Hi Andreas >> >> On Sun, Oct 20, 2013 at 8:46 PM, Andreas Kuckartz <a.kucka...@ping.de> wrote: >>> Hi Rupert, >>> >>>> with http://svn.apache.org/r1533921 the trunk now uses version 2.2.1. >>>> Created STANBOL-1182 for this task >>> >>> My log now says: >>> >>> [INFO] Started jetty 7.x.y-SNAPSHOT at port(s) HTTP:8765 on context path / >>> >>> (and that line appears twice ...) >>> >>> Jetty moved from Codehaus to Eclipse after version 7. Maybe that also >>> needs to be reflected in one or more of the pom.xml files somehow so >>> that Jetty 8 gets used ? >> >> The Jetty dependencies are not explicitly specified in any Stanbol >> pom. They are transitively added by the o.a.felix.http.jetty version. >> Based on maven.org version 2.2.1 of this bundle [1] depends on >> org.eclipse.jetty:jetty-server:7.6.12.v20130726. >> >> Ragarding Jetty 8 I found also [2]. >> >> If you still see Jetty to be initialized multiple times you could try >> to play around with the start levels in the osgiframework bundlelist. >> Currently "org.apache.felix.http.whiteboard" is started at level=5. >> The 'org.apache.felix.http.jetty' has level=1 - but as mentioned >> before - this is done in the pom.xml files of the launcher using >> jarWebSupport [3]. >> >> best >> Rupert >> >> >> >> [1] >> http://search.maven.org/#artifactdetails|org.apache.felix|org.apache.felix.http.jetty|2.2.1|jar >> [2] >> http://apache-felix.18485.x6.nabble.com/HTTP-Jetty-implementation-td5004509.html >> [3] >> http://sling.apache.org/site/maven-launchpad-plugin.html#MavenLaunchpadPlugin-ArtifactDefinition >> >>> >>> 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
