If maven is configured to use a proxy, the cuke4duke maven plugin only uses protocol/host/port combination while triggering the gem installation.
The plugin should add the username/password to the http-proxy argument too - otherwise the conenction to the outherworld fails!
If maven is configured to use a proxy, the cuke4duke maven plugin only uses protocol/host/port combination while triggering the gem installation. The plugin should add the username/password to the http-proxy argument too - otherwise the conenction to the outherworld fails!
e.g. if username/password is defined, it should not define the http-proxy like this: --http-proxy http://myproxy.com:8080 but like this: --http-proxy http://theuser:secret@myproxy.com:8080