In Fuse 6.1 Fabric profile communication goes via Maven Proxy

Issue

We setup a Maven proxy (see step 3 below) on the fabric profile, then used Maven to deploy a jar to the fabric Maven repository, eg:

mvn deploy:deploy-file -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0.3.0 -Dpackaging=jar -Dfile=ojdbc6.jar -DgeneratePom=true -Durl=http://admin:admin@10.66.218.98:8181/maven/upload

we found that fabric profile updates go through the proxy server. This is not a an acceptable situation because it means that the maven proxy is a single point of failure.

1. Setup a forward proxy using mod_proxy, ie:
Listen 172.17.42.1:9001

<IfModule mod_proxy.c>

ProxyRequests On
ProxyVia On

AllowCONNECT 443
AllowCONNECT 80

<Proxy *>
    Allow from all
</Proxy>
2. Create a 3 node fabric ensemble
3. Add a fabric maven proxy to the 'fabric' profile:
fabric:profile-edit --pid io.fabric8.maven/proxy.host=172.17.42.1 fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.port=9001 fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.protocol=http fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.nonProxyHosts=172.17.42.1 fabric
4. Upload a file to the Fabric Maven repository, ie:
mvn deploy:deploy-file -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0.3.0 -Dpackaging=jar -Dfile=ojdbc6.jar -DgeneratePom=true -Durl=http://admin:admin@localhost:8181/maven/upload
5. On one of the ensemble servers, do a 'fabric:create-profile'
6. Tail the forward proxy logs and observe that traffic goes through the proxy server