[jbosstools-issues] [JBoss JIRA] (JBIDE-12139) Proxy Settings - setting a proxy seems to cause Project Examples, News and Blogs to spin forever

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700065#comment-12700065 ] 

Andre Dietisheim commented on JBIDE-12139:
------------------------------------------

I am perfectly sure that using a proxy works with OpenShift - given the proxy is setup correctly (the squid and your prefs. I work with the OpenShift staging server which is only accessible when using a RedHat proxy (file.rdu.redhat.com:3128). The only problem that occurred there from time to time is that clonging was failing, but creating applications, domains, removing them etc. worked perfectly. I assume the proxy was then not allowing git operations.
                
> Proxy Settings - setting a proxy seems to cause Project Examples, News and Blogs to spin forever
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12139
>                 URL: https://issues.jboss.org/browse/JBIDE-12139
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>         Environment: CR1b
>            Reporter: Burr Sutter
>            Assignee: Snjezana Peco
>         Attachments: JBDS_Proxy_Settings.png, proxy.png
>
>
> I have been experimenting with an internally hosted maven repository for EAP6 - where I need to set a proxy in order to access that internal server.   Eclipse-Preferences-Network Connections allows you to establish a proxy - I certainly could have done it incorrectly.   But I also watched an end-user, who required a proxy for internal network server access struggle with JBDS - because JBDS could not find the newly created OpenShift application - it would always timeout.   
> Screenshot of my settings are attached - they should work on the VPN.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira