maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Maisonobe (JIRA)" <>
Subject [jira] [Commented] (MCHANGES-378) Github report does not use maven proxy settings
Date Thu, 28 Feb 2019 12:22:00 GMT


Luc Maisonobe commented on MCHANGES-378:

The report I made on Egit <> has
not seen
much trafic, however, a similar issue was raised and solved last december, see <>
and <>.

Could this be included in maven-changes-plugin now?

> Github report does not use maven proxy settings
> -----------------------------------------------
>                 Key: MCHANGES-378
>                 URL:
>             Project: Maven Changes Plugin
>          Issue Type: Bug
>          Components: github
>    Affects Versions: 2.12.1
>         Environment: Linux
>            Reporter: Luc Maisonobe
>            Priority: Major
> When attempting to run mvn:site on a project that uses GitHub as its SCM, maven-changes-plugin
gets called to create reports, and it always attempts to generate github-report (even despite
reportSet contains only changes-report and there is are changes.xml files in the various project
> An attempt to connect directly to on port 443 is then done, which is forbidden
by an authenticating proxy. This happens despite the proxy settings are correct in settings.xml
(and are used by other plugins).
> This looks similar to MCHANGES-231, but affects Github instead of JIRA.
> When using the -X switch to get some debug info, it seems the lowest level exception
is a (Connection Reset). The stack trace is:
> Caused by: Connection reset
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at org.eclipse.egit.github.core.client.GitHubClient.get(
> 	at
> 	at org.eclipse.egit.github.core.service.GitHubService.getAll(
> 	at org.eclipse.egit.github.core.service.IssueService.getIssues(
> 	at org.apache.maven.plugin.github.GitHubDownloader.getIssueList(
> 	at org.apache.maven.plugin.github.GitHubMojo.executeReport(
> So the connections is attempted by some code from egit. I was not able to find if the
problem is a wrong usage of egit from maven changes plugin or a bug in egit itself.

This message was sent by Atlassian JIRA

View raw message