maven-issues mailing list archives

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


Robert Scholte commented on MCHANGES-341:

I agree that we must be careful when specifying parameters, but a connection timeout sounds
very general for me. So my choice would be to keep it as the original commit and add to the
comments for which issue tracking systems it can be used, i.e just Jira for now. Otherwise
we could end up with 5 connectionTimeouts for 5 different issue systems which actually refer
to the same thing.

> 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