There has been reported behavior of a problem setting the http.nonProxyHosts system property and adding a features repository using the features:add command.

In this scenario the http.nonProxyHosts is being set in the karaf.bat script as a work around for ENTESB-590.

The use case also involves having the following properties set in the user's .m2 settings.xml:

<settings>
    <proxies>
        <proxy>
            <active>true</active>
            <protocol>http</protocol>
            <host>192.168.1.10</host>
            <port>80</port>
            <nonProxyHosts>192.*|*.example.com|192.168.1.15</nonProxyHosts>
        </proxy>
    </proxies>
</settings>

In etc/org.ops4j.pax.url.mvn.cfg I see the following option remains commented out:

#
# Uncomment if you are behind a web proxy. PAX URL will use the proxy settings
# from the Maven conf/settings.xml file
#
# org.ops4j.pax.url.mvn.proxySupport=true

When the container is first started the JVM properties can be inspected from JConsole or VisualVM to confirm the http.nonProxyHosts property is set.

Next, the features:addurl command is run to add a new features respository.

When the JVM properties are checked again the http.nonProxyHosts property is set to an empty string, however the http.proxyHost and http.proxyPort have been set with the values from the settings.xml file.