Hi, let me answer in reverse order:
3) rather ask here, you'll usually get a lot more feedback here :-) 2) it's by intention, the karaf maven plugin changed. You'll need to define a list of different features, take a look here [1] 1) The OSGiCommandSupport class isn't needed anymore, just use the Action Interface. You'll need to mark your command as service [2] With this you don't need a blueprint definition any more. regards, Achim [1] - https://github.com/ANierbeck/Karaf-Microservices-Tooling/blob/master/Karaf-Service-Runtime/pom.xml#L131-L143 [2] - https://github.com/ANierbeck/Karaf-Cassandra/blob/master/Karaf-Cassandra-Shell/src/main/java/de/nierbeck/cassandra/embedded/shell/CqlExecuter.java#L41 2015-11-10 21:28 GMT+01:00 Christian Lutz <[email protected]>: > Hello, > > today I started to update from karat 3.0.5 to 4.0.2 in this process I > stumbled across some questions you may be able to answer. > > 1. What is the correct replacement for the deprecated OsgiCommandSupport > class? > > 2. The feature <feature>standard</feature> is not available anymore within > the current org.apache.karaf.features.standard.xml, is it intended or a > bug? > If intended please update you minimal help distribution example > http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html > > 3. I asked a question on stackoverflow, what is your preferred channel for > questions? > > http://stackoverflow.com/questions/33626713/how-to-disable-karaf-maven-plugin-4-tight-dependency-constraint-checks > > Sincerely > Christian > > Env: Windows, JDK8, Maven 3.3.3 > > > > -- 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
