In order to resolve artifact from custom remote maven repository it is needed to set different configuration for "instal mvn:...." and "profile-edit --bundle mvn:...".

• settings for install command

  • profile-edit --pid io.fabric8.maven/io.fabric8.maven.settings='/home/fuse/http-proxy-settings.xml' default
    profile-edit --delete --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories default
    

  • custom http-proxy-settings.xml in attachment

• settigns for profile-edit command
  • etc/system.properties needs to specify http.proxyHost and http.proxyPort

  • profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories='http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-repo@id=fuse-qa' --append default

  • this settings is also sufficient for install command

So what is happening here?
In order to resolve artifact in profile which is exclusively fabric stuff you have to set karaf setting in system.properties file for local container (you have to do this manually for every spawned server in fabric). Imho this is wrong and just evil . Why "profile mvn handler" does not pick up proxy and repository from io.fabric8.maven/io.fabric8.maven.settings?

Why install command (which is local container staff) pick up proxy and repository config from fabric configuration io.fabric8.maven/io.fabric8.maven.settings? I would say install command should allways pick up config exclusively from etc/system.properties and repository from etc/org.ops4j.pax.url.mvn.cfg.

On the other side, profile-edit resolver should be configured fabric wide in some PID exclusively on fabric-maven-proxy level. So when any fabric container is requesting artifact which can't by satisfied locally fabric agent will ask fabric-maven-proxy where fabric wide proxy and repositories are set.