Thanks ... it's a rather intrusive behavioral change :) best to fix it now.
@Markus, you should consider to have a specialized Jenkins to verify your applications with recent snapshots so we can find those things earlier ;) regards, Achim 2016-08-25 9:57 GMT+02:00 Jean-Baptiste Onofré <[email protected]>: > OK, let me find the change in cause. > > I keep you posted. Then, I will cancel the release. > > Regards > JB > > > On 08/25/2016 09:52 AM, Markus Rathgeb wrote: > >> Hi, >> >> I was able to reproduce the issue Markus described with his test. >>>> One thing that crosses my mind, did we change something with the feature >>>> resolver? Cause I can't remember that the pax-web-api did actually >>>> contain >>>> a provide-capability for the WebContainer Service. >>>> >>> >> The feature that should be verified is using the pax-http-whiteboard >> and the http feature as dependency. >> See: https://github.com/maggu2810/k406-staging/blob/94794b8/featu >> re/src/main/feature/feature.xml#L10 >> >> So at least one bundle in that features should contain the >> WebContainer service, shouldn't it? >> The feature will introduce a lot more Pax Web bundles (not only the >> API), so the WebContainer implementation should be available. >> >> Do we consider as release blocker ? >>>> >>> >> If the verification of features is broken (and not only related to my >> features) I assume we should fix it for a release. Shouldn't we? >> >> Best regards, >> Markus >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
