[
https://issues.apache.org/jira/browse/MCHANGES-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luc Maisonobe updated MCHANGES-409:
-----------------------------------
Description:
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)
was:
When using changes plugin on a project hosted at GitHub, there is always
an attempt to connect to GitHub event 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 suppor 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 came would probably be useful also
for other reports)
> allow to completely skip github report
> --------------------------------------
>
> Key: MCHANGES-409
> URL: https://issues.apache.org/jira/browse/MCHANGES-409
> Project: Maven Changes Plugin
> Issue Type: Improvement
> 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.3.4#803005)
