maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MCHANGES-317) GitHub: "API rate limit exceeded"
Date Sat, 18 Mar 2017 02:38:41 GMT

    [ https://issues.apache.org/jira/browse/MCHANGES-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931017#comment-15931017
] 

Alex O'Ree commented on MCHANGES-317:
-------------------------------------

there is a way to work around this with code changes to the plugin. If a way to specify an
api key or username/password was added, then the rate limit is avoided

> GitHub: "API rate limit exceeded"
> ---------------------------------
>
>                 Key: MCHANGES-317
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-317
>             Project: Maven Changes Plugin
>          Issue Type: Bug
>          Components: github
>    Affects Versions: 2.9
>            Reporter: John Schneider
>
> I tried to generate a report and got this message:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site)
on project stax-mate: Error during page generation: Error rendering Maven report: API rate
limit exceeded for 149.###.###.##. See http://developer.github.com/v3/#rate-limiting for details.
(403) -> [Help 1]
> I think this is caused by having a low limit for unauthenticated requests. I think it
would be great if there was a way to authenticate...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message