[
https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353018#comment-353018
]
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: https://jira.codehaus.org/browse/MCHANGES-341
> Project: Maven Changes Plugin
> Issue Type: Improvement
> Reporter: Boris Pavlovic
> Assignee: Mirko Friedenhagen
> Fix For: 2.11
>
>
> [Based on the StackOverflow
> Question|http://stackoverflow.com/questions/25626369/how-to-configure-timeout-for-maven-changes-plugin/25627583#25627583]
> ----------------
> 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?
> ANSWER:
> 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
(v6.1.6#6162)
