Bug 509287 - Direct call to GitHubClient doesn't pass authenticating proxy
Summary: Direct call to GitHubClient doesn't pass authenticating proxy
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: GitHub (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-15 08:18 EST by luc CLA
Modified: 2016-12-15 14:28 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description luc CLA 2016-12-15 08:18:47 EST 
GitHubClient is used by the maven-changes-plugin to generate a github report.
This does not work from within a corporate network with an authenticating proxy between the host computer and the github server. The problem has been notified to maven change plugin team (see <https://issues.apache.org/jira/browse/MCHANGES-378>), and it appears to be related to GitHubclient (package org.eclipse.egit.github.core.client) not having suppot for proxy.

None of the attempted workaround worked (neither setting proxy via environment variables, via Java properties, via git config or via maven settings work).

This totally prevents maven-changes-plugin ot be used for a project hosted by GitHub and developed from within a corporate network.

Could such support be added?

Thanks