Hi Christian, I just looked through that feature file, since you need either the http-whiteboard feature or the jetty feature for it to run, are you sure about all those dependencies? Cause some of them like the activation-api should already be inlcuded by pax-jetty feature, no?
regards, Achim 2013/5/23 Jean-Baptiste Onofré <[email protected]> > +1 to limit the start levels. > > Regards > JB > > > On 05/23/2013 10:21 AM, Christian Schneider wrote: > >> I am currently working on: >> https://issues.apache.org/**jira/browse/CXF-5030<https://issues.apache.org/jira/browse/CXF-5030> >> >> It seems that we use an incorrect start level and order for the xmlsec >> dependency. I have just committed the fix for this. >> >> While correcting this I found that we have a lot of different start >> levels. I am quite sure we should not need all of these. >> >> I have created a wiki page with the current start levels and the meaning >> I figured out: >> https://cwiki.apache.org/**confluence/display/CXF20DOC/** >> CXF+feature+for+Apache+Karaf<https://cwiki.apache.org/confluence/display/CXF20DOC/CXF+feature+for+Apache+Karaf> >> >> >> Could you guys review this? I wonder if we could remove some of the >> start levels. >> I think we could limit it to just 9,10,20,30. >> >> Another issue is that there are also some duplicates in the bundles. For >> example we start the JAXB impls in cxf-specs and cxf-jaxb. >> >> What do you think? >> >> Christian >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
