users to use the --help option to check the name and type of arguments and options. In term of development, you can still use the blueprint definition as you do in Karaf 2.x & 3.x (with the corresponding (in org.apache.karaf.tooling Maven groupId). Take a look in the developer guide for the command development "new style" details. 3.3. Features repositories Karaf 4.x provides: • mvn:org.apache.karaf. SVN checkout, the Maven build and the dependencies Maven downloads. Environment: • Java SE Development Kit 1.8 or greater (http://www.oracle.com/technetwork/java/javase/). • Apache Maven 3.5.0 or greater

or SVN checkout, the Maven build and the dependencies Maven downloads. Environment: • Java SE Development Kit 1.7.x or greater (http://www.oracle.com/technetwork/ java/javase/). • Apache Maven 3.0.4 (http://maven software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software mirror git branch delivery archon/trunk # use it git checkout delivery # squash all your local development into a single commit git merge --squash trunk # commit it to the delivery branch git commit -m

checkout, the Maven build and the dependencies that Maven downloads. Environment: • Java SE Development Kit 1.7.x or greater ([http://www.oracle.com/technetwork/java/javase/]). • Apache Maven 3.0.3

checkout, the Maven build and the dependencies that Maven downloads. Environment: • Java SE Development Kit 1.7.x or greater ([http://www.oracle.com/technetwork/java/javase/]). • Apache Maven 3.0.3

(additional copies) of an index (1 by default): # #index.number_of_replicas: 1 # Note, that for development on a local machine, with small indices, it usually # makes sense to "disable" the distributed features: