Re: jboss-eap64-openshift quickstart maven proxy

2017-02-02 Thread Ben Parees
On Fri, Feb 3, 2017 at 12:15 AM, Lionel Orellana wrote: > Hi, > > This goes back a few months. I'm wondering if the issue Ben mentioned has > been fixed in 1.4? > > Basically have maven images respect standard proxy env variables. > ​Does not appear so: https://bugzilla.redhat.com/show_bug.cgi?

Re: jboss-eap64-openshift quickstart maven proxy

2017-02-02 Thread Lionel Orellana
Hi, This goes back a few months. I'm wondering if the issue Ben mentioned has been fixed in 1.4? Basically have maven images respect standard proxy env variables. Thanks. On 14 October 2016 at 11:00, Ben Parees wrote: > > > On Thu, Oct 13, 2016 at 6:14 PM, Lionel Orellana > wrote: > >> Thank

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Ben Parees
also the wildfly contains the same logic for configuring maven proxies, meaning it expects the same non-standard env variable: https://github.com/openshift-s2i/s2i-wildfly/blob/master/10.0/s2i/bin/assemble#L154 so i'm not sure why you didn't have the same problem with it. On Thu, Oct 13, 2016 at

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Ben Parees
On Thu, Oct 13, 2016 at 10:39 PM, Lionel Orellana wrote: > The Wildfly quickstarts work out of the box. Are the Wildfly and JBoss > builder images completely different? What's the relationship > between jboss-eap-6/eap64-openshift and openshift/wildfly-100-centos7? > ​yes they are completely dif

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Lionel Orellana
The Wildfly quickstarts work out of the box. Are the Wildfly and JBoss builder images completely different? What's the relationship between jboss-eap-6/eap64-openshift and openshift/wildfly-100-centos7? On 14 October 2016 at 11:00, Ben Parees wrote: > > > On Thu, Oct 13, 2016 at 6:14 PM, Lionel

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Ben Parees
On Thu, Oct 13, 2016 at 6:14 PM, Lionel Orellana wrote: > Thanks Jim. > > It worked by setting > > HTTP_PROXY_HOST=proxy.server.name > > and > > HTTP_PROXY_PORT=port > > > Are these supposed to be set globally by the Ansible scripts? I have > openshift_http_proxy, openshift_https_proxy, openshift

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Lionel Orellana
Thanks Jim. It worked by setting HTTP_PROXY_HOST=proxy.server.name and HTTP_PROXY_PORT=port 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 O

Re: jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Jim Minter
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]

jboss-eap64-openshift quickstart maven proxy

2016-10-13 Thread Lionel Orellana
Hi 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 org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.4.0.GA from/to central ( https://repo1.maven.org/maven2): Connectio