maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mirko Friedenhagen (JIRA)" <>
Subject [jira] (MCHANGES-341) Externalize JIRA server timeout values to the configuration section
Date Mon, 22 Sep 2014 19:39:10 GMT


Mirko Friedenhagen commented on MCHANGES-341:

[~rfscholte], while a general parameter might be feasible in the future, right now neither
Trac nor GitHub are an easy task to tackle as they hide their clients very deeply. In the
spirit of releasing more often, I would go for the {{jira*}} solution and when we have a more
general solution to take the unprefixed parameters as defaults for the other ones.

> Externalize JIRA server timeout values to the configuration section
> -------------------------------------------------------------------
>                 Key: MCHANGES-341
>                 URL:
>             Project: Maven Changes Plugin
>          Issue Type: Improvement
>            Reporter: Boris Pavlovic
>            Assignee: Mirko Friedenhagen
>             Fix For: 2.11
> [Based on the StackOverflow Question|]
> ----------------
> I have a maven-changes-plugin configured for a build process. Sometimes, JIRA intranet
server is down and the build takes ages waiting for a long timeout on JIRA.
> Is there a way to configure the timeout?
> It does not appear so. The source for the RestJiraDownloader, the class that queries
JIRA for issues, has hard-coded timeout values. Lines 562-566 indicate a connection timeout
of 36 seconds and a receive timeout of 32 seconds.

This message was sent by Atlassian JIRA

View raw message