6.5. Configuring Maven for FAB

FAB requires access to Maven repositories to download dependencies. The Maven configuration of FAB leverages the property settings of the Maven URL handler. This means that any changes to the Maven URL handler will have a ripple effect to other functions of the container. It also means that once a container is moved to a fabric, FAB uses the fabric's Maven proxy to resolve dependencies.

The properties used to configure a standalone container's Maven URL handler are in the org.ops4j.pax.url.mvn PID. See Section A.3, “Mvn URL Handler”.

A fabric container will also have a profile assigned to it that contains the org.ops4j.pax.url.mvn PID. This PID should not be modified for purposes of configuring FAB dependency resolution. Instead, you should modify the fabric's Maven proxy as described in chapter "Configuring a Fabric's Maven Proxy" in "Configuring and Running Red Hat JBoss Fuse".

If your local Maven repository is in a non-default location, you might find it necessary to configure it explicitly in order to access Maven artifacts that you have built locally. You can change the location of the local repository for a standalone container by setting the org.ops4j.pax.url.mvn PID's org.ops4j.pax.url.mvn.localRepository property to the location of your local Maven repository. Example 6.1, “Changing the Local Repository” shows the commands.

JBossFuse:karaf@root> config:edit org.ops4j.pax.url.mvn
JBossFuse:karaf@root> config:propset org.ops4j.pax.url.mvn.localRepository file:E:/Data/.m2/repository
JBossFuse:karaf@root> config:update

JBossFuse:karaf@root> config:edit org.ops4j.pax.url.mvn
JBossFuse:karaf@root> config:propset org.ops4j.pax.url.mvn.localRepository file:E:/Data/.m2/repository
JBossFuse:karaf@root> config:update

To customize the list of remote Maven repositories used by a standalone container, add or remove entries appearing in the comma-separated list in the org.ops4j.pax.url.mvn.repositories property value in the org.ops4j.pax.url.mvn.cfg PID.