I also came across this bug: https://issues.apache.org/jira/browse/KARAF-1657
which appears to be just a change to the comments in the sample config rather than any code change It implies that the plugin should be using the Maven proxy settings by default - but the error (below) suggests it did not try to use the proxy during a ServiceMix build. On 15/05/13 19:55, Daniel Pocock wrote: > > I've observed that the ServiceMix build fails when behind a proxy > > The Maven proxy settings are used for most things, but there is a karaf > plugin that tries to do direct network access, and it has been a problem > for other people building Karaf by itself: > > http://mail-archives.apache.org/mod_mbox/camel-users/201208.mbox/%3CCANZYW6aRgR%3DnpH1080a5XWpbKD9aakCU8OGCJH5ydg02rXjhsg%40mail.gmail.com%3E > >> [ERROR] Failed to execute goal >> org.apache.karaf.tooling:features-maven-plugin:2.2.8:add-features-to-repo >> (add-features-to-repo-win) on project dist: Can't resolve bundle >> com.google.code.scriptengines:scriptengines-jruby:jar:1.1: Could not >> transfer artifact com.google.code.s >> criptengines:scriptengines-jruby:jar:1.1 from/to >> http://scriptengines.googlecode.com/svn/m2-repo/ >> (http://scriptengines.googlecode.com/svn/m >> 2-repo/): Connection to http://scriptengines.googlecode.com refused >> [ERROR] >> com.google.code.scriptengines:scriptengines-jruby:jar:1.1 >> [ERROR] >> [ERROR] from the specified remote repositories: >> [ERROR] http://scriptengines.googlecode.com/svn/m2-repo/ >> (http://scriptengines.googlecode.com/svn/m2-repo/, releases=true, >> snapshots=true): >> Connection refused: connect > > > but the solution doesn't appear to work for a ServiceMix build > > I notice that during the build several copies of > > org.ops4j.pax.url.mvn.cfg are created within the tree. I tried adding the > correction to all of them and continuing the build, it didn't work. I also > tried adding > > -Dorg.ops4j.pax.url.mvn.proxySupport=true > > on the command line and that didn't work either. > > > The artifact it is trying to access is actually in the local mvn > ~/.m2/repository as well, it seems un-necessary that it has to make another > network access > > I have been able to run the build successfully on a machine that is not stuck > behind a proxy. > > Can anybody clarify how to proceed and do a full build either behind a proxy > or completely offline? > > >
