[jbosstools-issues] [JBoss JIRA] (JBIDE-12912) Identification of maven dependencies should work behind proxies

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-12912:
-------------------------------------

Fixed with commit https://github.com/jbosstools/jbosstools-central/commit/0cc028112376024eada177e6975760b5a7a41e0e

No ITs provided as we have no easy way to test proxy usage.

Smoke tested against the file.rdu.redhat.com:3128 proxy :
* Use case from JBIDE-12702 (identify groovy jars)
* proxy configured but VPN off : groovy jars can't be identified
* proxy configured and VPN on : groovy jars are identified
* no proxy : groovy jars are identified



                
> Identification of maven dependencies should work behind proxies
> ---------------------------------------------------------------
>
>                 Key: JBIDE-12912
>                 URL: https://issues.jboss.org/browse/JBIDE-12912
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 4.0.0.Beta1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.CR1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> When querying remote nexus repos or maven central for jar identification, the http connection doesn't use the Eclipse proxy settings, rendering the feature useless when working behind proxies.
> We'd need a dev proxy in order to dev/test against that sort of scenario

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira