This is a double post after subscribing to the mailing list... Hi Scott,
yes we have configured http-proxy in the settings.xml. We also tried setting system-properties by using -Dhttp.proxyHost and -Dhttp.proxyPort, but it did not help. It seems as if the org.apache.karaf.tooling:features-maven-plugin does not take over the proxy configurations. We also installed the not-accessible .jars into our local repository prior to the build, but this also does not help. Inside the file apache-camel-2.9.2-features.xml there are entries like these: <bundle>mvn:http://scriptengines.googlecode.com/svn/m2-repo/!com.google.code.scriptengines/scriptengines-jruby/1.1<http://scriptengines.googlecode.com/svn/m2-repo/%21com.google.code.scriptengines/scriptengines-jruby/1.1> </bundle> which cause maven to ignore the local repository and instead search in the internet for the referenced library. A notation like mvn:groupId:artifactId:version would probably help at this point. Is there any solution for this problem? -- View this message in context: http://camel.465427.n5.nabble.com/Can-not-use-Karaf-Camel-feature-behind-HTTP-proxy-tp5718267p5718713.html Sent from the Camel - Users mailing list archive at Nabble.com.
