Properties 4.8.2. Files 4.8.3. config:* commands 4.8.4. JMX ConfigMBean 4.9. Artifacts repositories and URLs 4.9.1. Maven URL Handler 4.9.2. Maven configuration commands 4.10. Provisioning 4.10.1. Application centralizes the configuration in one file. • Provisioning: Apache Karaf supports a large set of URLs where you can install your applications (Maven repository, HTTP, file, etc). It also provides the map. 4.9. Artifacts repositories and URLs The main information provided by a feature is the set of OSGi bundles that defines the application. Such bundles are URLs pointing to the actual bundle jars.

69 Artifacts repositories and URLs // TODO temp The main information provided by a feature is the set of OSGi bundles that defines the application. Such bundles are URLs pointing to the actual bundle pax.url.mvn bundle resolves mvn URLs. It can be configured using the file etc/org.ops4j.pax.url.cfg The most important property is : 70 ARTIFACTS REPOSITORIES AND URLS • org.ops4j.pax.url.mvn.repositories repositories : Comma separated list of repository remote repository URLs that are checked in order of occurence when resolving maven artifacts By default, snapshots are disabled. To enable an URL for snapshots

• features • eventadmin Optionally, Cellar also support synchronization of OSGi EventAdmin, OBR (URLs and bundles). The second purpose is to provide a Distributed OSGi runtime. It means that using Cellar cluster default.obr.urls.sync = cluster karaf@node1()> cluster:sync Synchronizing cluster group default bundle: done config: done feature: done obr.urls: No synchronizer found for obr.urls It’s also possible for bundle • -f (--feature) for feature • -c (--config) for configuration • -o (--obr) for OBR URLs or a given cluster group using the -g (--group) option. 5.5. Producer, consumer, and handlers To

local) * config * features Optionally, Cellar also support synchronization of OSGi EventAdmin, OBR (URLs and bundles). The second goal is to provide a Distributed OSGi runtime. It means that using Cellar default.bundle.sync = cluster default.config.sync = cluster default.feature.sync = cluster default.obr.urls.sync = cluster It’s also possible to sync only a resource using: • -b ( --bundle ) for bundle • • -f ( --feature ) for feature • -c ( --config ) for configuration • -o ( --obr ) for OBR URLs or a given cluster group using the -g ( --group ) option. 5.5. Producer, consumer, and handlers To notify

the repositories. • Artifact Upload: Users can upload OSGi bundle in a Cave repository. It supports URLs like mvn:groupId/artifactId/version, file:, http:, etc. • Repository proxy: Cave is able to proxy on the "external" repository, Cave handles the repository metadata. Cave supports file: and http: URLs, it means that Cave is able to browse a remote HTTP Maven repository for instance. • Repository

RepositoryAdmin OSGi service. • Artifact Upload: Users can upload OSGi bundle in a Cave repository. It supports URLs like mvn:groupId/artifactId/version , file: , http: , etc. • Repository proxy: Karaf Cave is able located on the "external" repository, Cave handles the OBR metadata. Cave supports file: and http: URLs, it means that Cave is able to browse a remote HTTP Maven repository for instance. • Repository