Re: MCHANGES-341: Best way to configure specific Mojo

2014-09-19 Thread Mirko Friedenhagen
Thanks for your feedback, so I will add parameters. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Fri, Sep 19, 2014 at 9:16 PM, Karl Heinz Marbaise wrote: > Hi, > > >> Hi, >

Re: MCHANGES-341: Best way to configure specific Mojo

2014-09-19 Thread Karl Heinz Marbaise
Hi, > Hi, My guess is that javadoc:javadoc holds the record[1]. If i count correctly 98 parameters..wow...i didn't expect being so much... For remote systems a timeout parameter makes sense. I would expect that users are familiar with the parameter pages. Yes this is the source of inform

Re: MCHANGES-341: Best way to configure specific Mojo

2014-09-19 Thread Robert Scholte
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.

MCHANGES-341: Best way to configure specific Mojo

2014-09-18 Thread Mirko Friedenhagen
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 J