Le 12 décembre 2011 16:21, Arnaud Héritier <[email protected]> a écrit : http://maven.apache.org/docs/3.0.4/release-notes.html > +1 to have it set to 5 or 10 minutes by default and with a big warning and
I will setup to 30 minutes. (don't know yet if need a wagon release or not will see later) > associated doc in the release note Already prepared: http://maven.apache.org/docs/3.0.4/release-notes.html BTW I'm very happy to see some discussions here, I hope this release will be here one day :-) > Even if I understand Brian about the "why do we fix something not reported > as broken", I would better consider it as an improvement and not a fix. > Do we have to release a 3.1 just for this improvement .... I'm not sure... > Do we want to wait for a 3.1 to include it ... I'm less sure ... > > > On Mon, Dec 12, 2011 at 4:04 PM, Igor Fedorenko <[email protected]> wrote: > >> m2e has read timeout of 60s by default (IDE is different environment, >> we can't afford blocking build thread forever). There were >> bugreports about this. Some corporate users reported wait times in tens >> of minutes due to conservative firewall setup that fully downloads >> artifacts and does antivirus scan before serving the artifact to the >> client. >> >> -- >> Regards, >> Igor >> >> >> On 11-12-12 9:45 AM, Olivier Lamy wrote: >> >>> 2011/12/12 Brian Fox<[email protected]>: >>> >>>> Agree. >>>>> I will add it in release and complete documentation here: >>>>> http://maven.apache.org/**guides/mini/guide-http-**settings.html<http://maven.apache.org/guides/mini/guide-http-settings.html> >>>>> >>>> >>>> >>>> This seems like a pretty big change and not enough people will read >>>> that and start to freak out. If maven worked all this time with no >>>> read timeout, why change it now? I've never been aware of it causing a >>>> problem and this is just begging for all kinds of bug reports and >>>> flaming blogs. >>>> >>> >>> If any remote repository/server hang, I'm still thinking not wait >>> infinitely a response from a server is a good idea and will provide a >>> better user experience. (sure IMHO) >>> >>> BTW 60s value is maybe to small. >>> What would you prefer as value ? 300s ? >>> >>> Note this value is the SO_TIMEOUT which is the value before receiving >>> the first packet or the maximum of inactivity time between 2 packets. >>> >>> >>> >>>> >>>> >>>>> >>>>>> - Brett >>>>>> >>>>>> -- >>>>>> Brett Porter >>>>>> [email protected] >>>>>> http://brettporter.wordpress.**com/<http://brettporter.wordpress.com/> >>>>>> http://au.linkedin.com/in/**brettporter<http://au.linkedin.com/in/brettporter> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------**------------------------------** >>>>>> --------- >>>>>> To unsubscribe, e-mail: >>>>>> [email protected].**org<[email protected]> >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Olivier Lamy >>>>> Talend: http://coders.talend.com >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>>> >>>>> ------------------------------**------------------------------** >>>>> --------- >>>>> To unsubscribe, e-mail: >>>>> [email protected].**org<[email protected]> >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> To unsubscribe, e-mail: >>>> [email protected].**org<[email protected]> >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> >>> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> [email protected].**org<[email protected]> >> For additional commands, e-mail: [email protected] >> >> -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
