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 10:43 PM, Ben Parees <[email protected]> wrote: > > > On Thu, Oct 13, 2016 at 10:39 PM, Lionel Orellana <[email protected]> > 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 different, maintained by different teams. There > is a similarity of philosophy and original design, but otherwise they are > independent. > > > > > >> >> On 14 October 2016 at 11:00, Ben Parees <[email protected]> wrote: >> >>> >>> >>> On Thu, Oct 13, 2016 at 6:14 PM, Lionel Orellana <[email protected]> >>> 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_no_proxy and >>>> openshift_generate_no_proxy_hosts in my inventory file. >>>> >>> >>> no, unfortunately those values are very specific to those particular >>> images. That said, we have an open issue to have those images updated to >>> respect the more standard proxy env variables. >>> >>> >>> >>> >>>> >>>> On 13 October 2016 at 19:25, Jim Minter <[email protected]> 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/s >>>>> ingle/red-hat-xpaas-eap-image/#environment_variables_3 >>>>> [2] https://docs.openshift.com/container-platform/3.3/install_co >>>>> nfig/build_defaults_overrides.html >>>>> >>>>> Cheers, >>>>> >>>>> Jim >>>>> >>>>> -- >>>>> Jim Minter >>>>> Principal Software Engineer, Red Hat UK >>>>> >>>>> >>>>> On 13/10/16 08:27, Lionel Orellana wrote: >>>>> >>>>>> 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 >>>>>> <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? >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> users mailing list >>>>>> [email protected] >>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>>>> >>>>>> >>>> >>>> _______________________________________________ >>>> users mailing list >>>> [email protected] >>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>> >>>> >>> >>> >>> -- >>> Ben Parees | OpenShift >>> >>> >> > > > -- > Ben Parees | OpenShift > > -- Ben Parees | OpenShift
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
