I think this summarizes a core maintenance issue with pax+karaf today > I am not sure how many people travel between PAX and Karaf and vice versa, > but lets be honest - contribution criteria for PAX is lower than for Karaf.
I suggest we take a look at migrating pax-* (pax-logging. pax-url, pax-web, etc) into karaf for a couple of practical benefits (perhaps for Karaf 4.5?): 1. Less repositories to manage and preform releases 2. Artifacts (jars, configs, services) are less confusing to users (ie. org.apache.karaf.web makes more sense vs org.ops4j.pax.web .. etc) This would also give us an opportunity to see how this gels before finalizing what is supported in Karaf 5 (jetty, tomcat, etc). Thoughts? Matt Pavlovich
