[
https://issues.apache.org/jira/browse/MCHANGES-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902134#comment-17902134
]
Luc Maisonobe commented on MCHANGES-409:
----------------------------------------
The configuration that did not work at the time this issue was filed
corresponds to the [Hipparchus
project|[https://github.com/Hipparchus-Math/hipparchus/],] which is a
multi-module project. The code corresponding to that time can be found in the
release-1.7 branch (which is an old one by now). The current settings in the
master branch seem quite similar to the ones in release-1.7 (see
[hipparchus-parent/pom.xml line
954|[https://github.com/Hipparchus-Math/hipparchus/blob/3703d6560c1e12ef70150686e98516f7c5ec93af/hipparchus-parent/pom.xml#L954]).|https://github.com/Hipparchus-Math/hipparchus/blob/3703d6560c1e12ef70150686e98516f7c5ec93af/hipparchus-parent/pom.xml#L954])]
I unfortunetely cannot check the behaviour related to the proxy filtering
anymore. Now I am doing the development from a different network and connection
is seemless, I cannot reproduce the problem anymore.
> allow to completely skip github report
> --------------------------------------
>
> Key: MCHANGES-409
> URL: https://issues.apache.org/jira/browse/MCHANGES-409
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
> Affects Versions: 2.12.1
> Reporter: Luc Maisonobe
> Priority: Major
>
> When using changes plugin on a project hosted at GitHub, there is always
> an attempt to connect to GitHub even when reportSet contains *only*
> changes-report and nothing related to GitHub.
>
> This creates several problems. The first one was already identified with
> MCHANGES-378 with
> the subsequents request MCHANGES-396 which are not yet solved.
>
> A new one arose in recent days as GitHub does not support username/password
> authentication anymore and MCHANGES-400 seems to prevent connecting otherwise.
>
> So basically for now, being hosted at GitHub completely prevents using
> maven-changes-plugin since it mandates connecting to an host that mandates an
> authentication method that is not supported. And this even when you do *not*
> want the GitHub report at all.
>
> So it would be nice to have a configuration parameter that allows to
> completely skip attempts to connect to GitHub (and the same would probably be
> useful also for other reports)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
