Hi, Am 10.11.2012 um 22:24 schrieb Robert Munteanu:
> Just to complete the below information, updating the version of the > org.apache.felix.http.jetty bundle only works when it is set in the > maven-launchpad-plugin configuration/jarWebSupport element. > > This seems a bit strange to me, should I file a bug? No, this is by intent: Http Service support is specific to whether the Sling Launchpad is built as a Java Application (in which case the Jetty based Http Service is used) or a Web Application (in which case the Http Service bridge is used). The bundle list is used for the rest of the system, which does not care about these deployment details. Regards Felix > > Robert > >> >> I've noticed that indeed the updated configuration properties are only >> available for org.apache.felix.http.jetty 2.2.1-SNAPSHOT for now. I've tried >> including the updated http bundle in the launchpad, but that seems to have no >> effect. I've tried: >> >> - configuring the maven-launchpad-plugin >> >> <configuration> >> <defaultBundleList> >> <version>6</version> >> </defaultBundleList> >> <additionalBundles> >> <bundle> >> >> <groupId>org.apache.felix</groupId> >> >> <artifactId>org.apache.felix.http.jetty</artifactId> >> >> <version>2.2.1-SNAPSHOT</version> <!-- >> pick up fixes for setting context path and bind host --> >> >> </bundle> >> </additionalBundles> >> </configuration> >> >> - updating the list.xml bundle list >> >> <startLevel level="5"> >> <bundle> >> <groupId>org.apache.felix</groupId> >> <artifactId>org.apache.felix.http.jetty</artifactId> >> <version>2.2.1-SNAPSHOT</version> <!-- pick up fixes for setting >> context path and bind host --> >> </bundle> >> </startLevel> >> >> >> but they both have the same result: >> >> $ find target/classes/resources/ -name org.apache.felix.http.jetty\* >> target/classes/resources/bundles/0/org.apache.felix.http.jetty-2.2.0.jar >> >> What am I doing wrong? >> >> Thanks, >> >> Robert >> >>> >>> Regards >>> Felix
