[
https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352972#comment-352972
]
Dennis Lundberg commented on MCHANGES-341:
------------------------------------------
I'm sure that this is well documented. That is not the problem. The parameters
you mention was most likely added when JIRA was the only supported "external"
issue management system. Hence there was no need at the time to prefix them
with "jira". We might consider deprecating those parameters and introducing new
ones with a prefix, but that's another issue :-)
My concern is what happens when the Trac or Github fetchers wants a similar
parameter. In my opinion it is wise at this time to prefix a new parameter with
the issue management system it is used for, if it only works for one. If the
parameter works for all issue management systems then there is no need for a
prefix.
> 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)
