[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: jboss-eap64-openshift quickstart maven proxy

Thanks Jim. 

It worked by setting 




Are these supposed to be set globally by the Ansible scripts? I have openshift_http_proxy, openshift_https_proxy, openshift_no_proxy and openshift_generate_no_proxy_hosts in my inventory file. 

On 13 October 2016 at 19:25, Jim Minter <jminter redhat com> wrote:
Hi Lionel,

It should be a case of setting the HTTP_PROXY_HOST environment variable.  (I'm not sure why it's not just plain HTTP_PROXY - sorry).  See [1].

Also note that you can predefine this and other environment variables used at build time globally across the cluster if you like [2].

[1] https://access.redhat.com/documentation/en/red-hat-xpaas/0/single/red-hat-xpaas-eap-image/#environment_variables_3
[2] https://docs.openshift.com/container-platform/3.3/install_config/build_defaults_overrides.html



Jim Minter
Principal Software Engineer, Red Hat UK

On 13/10/16 08:27, Lionel Orellana wrote:

I'm trying to run the jboss-eap64-openshift quickstart but the build is
failing to download from maven central.

[ERROR] Non-resolvable import POM: Could not transfer artifact
<http://6.4.0.GA> from/to central
(https://repo1.maven.org/maven2):Connection to https://repo1.maven.org
<https://repo1.maven.org/>refused @ line 71, column 25

I had no problems with the Wildfly quickstarts.

I tried setting proxyHost and proxyPort in MAVEN_OPTS but that did nothing.

Do I really have to clone the repo and modify the maven settings.xml
file to run the quickstart? How come Wildfly works?


users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]