[
https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352986#comment-352986
]
Mirko Friedenhagen edited comment on MCHANGES-341 at 9/22/14 3:10 AM:
----------------------------------------------------------------------
I took a look into the Github and Trac downloaders and there does not seem to
be a simple way set timeouts, the clients are set up in depending libraries, so
I committed http://svn.apache.org/viewvc?view=revision&revision=1626681. Thanks
for your feedback, Dennis.
Uploaded new SNAPSHOT
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-changes-plugin/2.11-SNAPSHOT/maven-changes-plugin-2.11-20140922.080939-195.pom
was (Author: mfriedenhagen):
I took a look into the Github and Trac downloaders and there does not seem to
be a simple way set timeouts, the clients are set up in depending libraries, so
I committed http://svn.apache.org/viewvc?view=revision&revision=1626681. Thanks
for your feedback, Dennis.
> 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)
