On 16/05/13 09:54, Freeman Fang wrote: > Hi, > > Pass system properties about http proxy into your maven should work, > > something like -Dhttp.proxyHost=your_proxy_host > -Dhttp.proxyPort=your_proxy_port, etc
It still doesn't help - it always fails at exactly the same spot, and the root cause is from org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon rather than regular Java HTTP connection code, so I suspect that setting is being ignored. The maven .m2/settings.xml proxy settings work fine for everything else up to this point in the build. Notice the exception says it was trying to connect directly to the host, it doesn't mention the proxy at all: [ERROR] Failed to execute goal org.apache.karaf.tooling:features-maven-plugin:2.2.10:add-features-to-repo (add-features- to-repo) on project apache-servicemix-full: Can't resolve bundle com.google.code.scriptengines:scriptengines-jruby:jar:1 .1: Could not transfer artifact com.google.code.scriptengines:scriptengines-jruby:jar:1.1 from/to http://scriptengines.g ooglecode.com/svn/m2-repo/ (http://scriptengines.googlecode.com/svn/m2-repo/): Connection to http://scriptengines.google code.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=tru e, snapshots=true): Connection timed out: connect [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.karaf.tooling:features-maven-p lugin:2.2.10:add-features-to-repo (add-features-to-repo) on project apache-servicemix-full: Can't resolve bundle com.goo gle.code.scriptengines:scriptengines-jruby:jar:1.1 Caused by: org.apache.maven.wagon.providers.http.httpclient.conn.HttpHostConnectException: Connection to http://scripten gines.googlecode.com refused at org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultClientConnectionOperator.openConnection(Def aultClientConnectionOperator.java:190) at org.apache.maven.wagon.providers.http.httpclient.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConn ectionImpl.java:294) at org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector.tryConnect(DefaultRequest Director.java:645) at org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector.execute(DefaultRequestDir ector.java:480) at org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.ja va:906) at org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.ja va:805) at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:746) at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.resourceExists(AbstractHttpClientWagon.java:665) ... 5 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at
