Hi,
My guess is that javadoc:javadoc holds the record[1].
For remote systems a timeout parameter makes sense.
I would expect that users are familiar with the parameter pages.
If you start introducing an environment variable, it'll become a hidden
feature only visible to those few who read FAQs.
thanks,
Robert
[1] http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
Op Thu, 18 Sep 2014 22:24:47 +0200 schreef Mirko Friedenhagen
<[email protected]>:
Hello everybody,
I want to take a stance at above issue[1]. REST-requests to JIRA
timeout after +- 30 seconds right now. Internally we use a
misconfigured JIRA instance where the call to the status-URL needs 4
minutes (400.000 issues with 400 resolutions, that is what happens
when 120 people are JIRA-admins ;-))!
Should I just add additional parameters to the announcement-generate,
announcement-mail and jira-report?
Maybe it would be better to use environment variables as these mojo
already have loads of configuration parameters and the use case is
very specific.
What do you think?
Best Regards
Mirko
[1] https://jira.codehaus.org/browse/MCHANGES-341 Externalize JIRA
server timeout values to the configuration section
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
