Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I also think that 60s timeout is way too short for corporate users. I suggest something like at least 180s (500s would be even better). If we go with 60s, I know for sure that it will fail for most of my corporate customers and Maven will be the focus of some more bad talks. Please don't do this - it will be bad for Maven! Those that want to lower timeout could configure that. A third digit release should not have a big impact on your environment. As someone pointed out, in most corporate environments downloads are scanned by AV engines. And that means that the entire file needs to be downloaded by that engine and then scanned, before made available to the repo manager. So this isn't something that the repo manager could fix. /Anders On Mon, Dec 12, 2011 at 16:21, Arnaud Héritier aherit...@gmail.com wrote: +1 to have it set to 5 or 10 minutes by default and with a big warning and associated doc in the release note 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: Agree. I will add it in release and complete documentation here: http://maven.apache.org/**guides/mini/guide-http-**settings.htmlhttp://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 br...@apache.org http://brettporter.wordpress.**com/http://brettporter.wordpress.com/ http://au.linkedin.com/in/**brettporterhttp://au.linkedin.com/in/brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Same for MRMs, to perform checksum/signature/content analysis... to be able to cleanly refuse maven when asking for broken artifact (and having checksum/signature/content validation on). Otherwise, if would be done while streaming, currently there's no clean way to say to client (Maven) at _the end_ of streaming: ah, this is bad content, throw it away... Thanks, ~t~ On Tue, Dec 13, 2011 at 9:24 AM, Anders Hammar and...@hammar.net wrote: As someone pointed out, in most corporate environments downloads are scanned by AV engines. And that means that the entire file needs to be downloaded by that engine and then scanned, before made available to the repo manager. So this isn't something that the repo manager could fix. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? On Tue, Dec 13, 2011 at 9:24 AM, Anders Hammar and...@hammar.net wrote: I also think that 60s timeout is way too short for corporate users. I suggest something like at least 180s (500s would be even better). If we go with 60s, I know for sure that it will fail for most of my corporate customers and Maven will be the focus of some more bad talks. Please don't do this - it will be bad for Maven! Those that want to lower timeout could configure that. A third digit release should not have a big impact on your environment. As someone pointed out, in most corporate environments downloads are scanned by AV engines. And that means that the entire file needs to be downloaded by that engine and then scanned, before made available to the repo manager. So this isn't something that the repo manager could fix. /Anders On Mon, Dec 12, 2011 at 16:21, Arnaud Héritier aherit...@gmail.com wrote: +1 to have it set to 5 or 10 minutes by default and with a big warning and associated doc in the release note 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: 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 br...@apache.org http://brettporter.wordpress.**com/ http://brettporter.wordpress.com/ http://au.linkedin.com/in/**brettporter http://au.linkedin.com/in/brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. On Tue, Dec 13, 2011 at 9:24 AM, Anders Hammar and...@hammar.net wrote: I also think that 60s timeout is way too short for corporate users. I suggest something like at least 180s (500s would be even better). If we go with 60s, I know for sure that it will fail for most of my corporate customers and Maven will be the focus of some more bad talks. Please don't do this - it will be bad for Maven! Those that want to lower timeout could configure that. A third digit release should not have a big impact on your environment. As someone pointed out, in most corporate environments downloads are scanned by AV engines. And that means that the entire file needs to be downloaded by that engine and then scanned, before made available to the repo manager. So this isn't something that the repo manager could fix. /Anders On Mon, Dec 12, 2011 at 16:21, Arnaud Héritier aherit...@gmail.com wrote: +1 to have it set to 5 or 10 minutes by default and with a big warning and associated doc in the release note 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: 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 br...@apache.org http://brettporter.wordpress.**com/ http://brettporter.wordpress.com/ http://au.linkedin.com/in/**brettporter http://au.linkedin.com/in/brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Even if they are not scanned by AV - repo managers may be verifying the checksums of the downloaded files before sending them on. /James -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: 13 December 2011 08:25 To: Maven Developers List Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged I also think that 60s timeout is way too short for corporate users. I suggest something like at least 180s (500s would be even better). If we go with 60s, I know for sure that it will fail for most of my corporate customers and Maven will be the focus of some more bad talks. Please don't do this - it will be bad for Maven! Those that want to lower timeout could configure that. A third digit release should not have a big impact on your environment. As someone pointed out, in most corporate environments downloads are scanned by AV engines. And that means that the entire file needs to be downloaded by that engine and then scanned, before made available to the repo manager. So this isn't something that the repo manager could fix. /Anders On Mon, Dec 12, 2011 at 16:21, Arnaud Héritier aherit...@gmail.com wrote: +1 to have it set to 5 or 10 minutes by default and with a big warning +and associated doc in the release note 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: Agree. I will add it in release and complete documentation here: http://maven.apache.org/**guides/mini/guide-http-**settings.htmlh ttp://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 br...@apache.org http://brettporter.wordpress.**com/http://brettporter.wordpress. com/ http://au.linkedin.com/in/**brettporterhttp://au.linkedin.com/in /brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscribe@maven.apache.o rg For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.or g For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
30 minutes is a high enough value that I think we'll be ok. Thanks Olivier. On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
If you are cutting a new RC, does that mean that my recent fix creeps in? On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
No. There is a branch http://svn.apache.org/repos/asf/maven/maven-3/branches/maven-3.0.4-RCx/ . This branch is to track more easily changes between RC and to not prevent enthusiast hacker to commit in trunk. 2011/12/13 Benson Margulies bimargul...@gmail.com: If you are cutting a new RC, does that mean that my recent fix creeps in? On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I presume you mean enthusiastic hacker and not enthusiast hacker as the latter would be closer to amateur hacker and I don't know that we consider PMC members amateur hackers... unless we have set the bar too low ;-) On 13 December 2011 17:08, Olivier Lamy ol...@apache.org wrote: No. There is a branch http://svn.apache.org/repos/asf/maven/maven-3/branches/maven-3.0.4-RCx/ . This branch is to track more easily changes between RC and to not prevent enthusiast hacker to commit in trunk. 2011/12/13 Benson Margulies bimargul...@gmail.com: If you are cutting a new RC, does that mean that my recent fix creeps in? On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
sorry due to my french native language, I don't know all the english language refinement especially very fine ones :-) (I have enough to learn in french!) 2011/12/13 Stephen Connolly stephen.alan.conno...@gmail.com: I presume you mean enthusiastic hacker and not enthusiast hacker as the latter would be closer to amateur hacker and I don't know that we consider PMC members amateur hackers... unless we have set the bar too low ;-) On 13 December 2011 17:08, Olivier Lamy ol...@apache.org wrote: No. There is a branch http://svn.apache.org/repos/asf/maven/maven-3/branches/maven-3.0.4-RCx/ . This branch is to track more easily changes between RC and to not prevent enthusiast hacker to commit in trunk. 2011/12/13 Benson Margulies bimargul...@gmail.com: If you are cutting a new RC, does that mean that my recent fix creeps in? On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/13 Olivier Lamy ol...@apache.org: 2011/12/13 Brett Porter br...@apache.org: On 13/12/2011, at 7:38 PM, Olivier Lamy wrote: Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit : Olivier increased it to 30 min https://jira.codehaus.org/browse/WAGON-365 http://svn.apache.org/viewvc?view=revisionrevision=1213414 Thus I suppose we have to prepare another RC ? Is there others feedback to listen before launching another RC ? Others problems with the RC3 ? need a wagon release first. Wouldn't it be possible to do this in Maven, same as the user agent setting? With something hackhish sure :-) I can in DefaultMaven#newRepositorySession L416 modify/add/manipulate on the fly a XmlPlexusConfiguration and add the readTimeout element if not already set. So it works but definitely I find that too much hackhish :-) I configure wagon with a default configuration +configuration + +httpConfiguration + +all + + readTimeout180/readTimeout + +/all + +/httpConfiguration+ +/configuration; In case of already existing configuration the dom is merged. But as some wagon doesn't have those fields available (ssh, webdav) there are some warning in the logs. I definitely prefer release wagon 2.2 as those warning will generate too much confusion. So we can wait 1/2 more weeks again :-) In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
At this rate Aether and Sisu will probably have finally passed thru Eclipse and we can start the process all over again ;-) Mark -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Dec 14, 2011 at 7:44 AM, Olivier Lamy ol...@apache.org wrote: So we can wait 1/2 more weeks again :-)
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/13 Mark Derricutt m...@talios.com: At this rate Aether and Sisu will probably have finally passed thru Eclipse and we can start the process all over again ;-) possible :-) BTW that's good to take care of quality (especially using RC candidate release model :P ) Mark -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Dec 14, 2011 at 7:44 AM, Olivier Lamy ol...@apache.org wrote: So we can wait 1/2 more weeks again :-) -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I definitely prefer release wagon 2.2 as those warning will generate too much confusion. 2.1.1 instead of 2.2? So we can wait 1/2 more weeks again :-) In wagon trunk I have added more methods in Wagon api level to set this timeout (will be better) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/12 Brett Porter br...@apache.org: I've noticed a potential problem when using a repository manager. The new wagon library seems to have introduced a read time out: Could not transfer artifact [...]: Read timed out - [Help 1] This is going to fail the first time you hit an artifact proxied by a repository manager that takes more than 1 minute to download because there is no progress on the read. In previous versions, there was only a connection timeout. I think that needs to be prevented, at least until the repository managers all stream proxied artifacts so there is some download progress to report. You mean removing SO_TIMEOUT ? Perso I think it's good to have such value to prevent infinite wait when the remote server hangs for any reason. Currently the default value is 60s. Do you think this value must be increase or at least more easily configurable tru cli or removed and replace with a infinite value ? Last but not least do we have to consider this as blocker for the release ? Cheers, Brett On 06/12/2011, at 1:28 AM, Olivier Lamy wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
On 12/12/2011, at 7:42 PM, Olivier Lamy wrote: 2011/12/12 Brett Porter br...@apache.org: I've noticed a potential problem when using a repository manager. The new wagon library seems to have introduced a read time out: Could not transfer artifact [...]: Read timed out - [Help 1] This is going to fail the first time you hit an artifact proxied by a repository manager that takes more than 1 minute to download because there is no progress on the read. In previous versions, there was only a connection timeout. I think that needs to be prevented, at least until the repository managers all stream proxied artifacts so there is some download progress to report. You mean removing SO_TIMEOUT ? Perso I think it's good to have such value to prevent infinite wait when the remote server hangs for any reason. Currently the default value is 60s. Do you think this value must be increase or at least more easily configurable tru cli or removed and replace with a infinite value ? I didn't realise it could already be configured via settings.xml. It should be specifically called to attention in the docs and the release notes. An enhancement later could be to direct someone to an explanation in the error message. Last but not least do we have to consider this as blocker for the release ? Some way of addressing it (at a minimum clear docs) should be with the release. I would imagine this ending up causing complaints to repository manager user lists pretty quickly otherwise. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/12 Brett Porter br...@apache.org: On 12/12/2011, at 7:42 PM, Olivier Lamy wrote: 2011/12/12 Brett Porter br...@apache.org: I've noticed a potential problem when using a repository manager. The new wagon library seems to have introduced a read time out: Could not transfer artifact [...]: Read timed out - [Help 1] This is going to fail the first time you hit an artifact proxied by a repository manager that takes more than 1 minute to download because there is no progress on the read. In previous versions, there was only a connection timeout. I think that needs to be prevented, at least until the repository managers all stream proxied artifacts so there is some download progress to report. You mean removing SO_TIMEOUT ? Perso I think it's good to have such value to prevent infinite wait when the remote server hangs for any reason. Currently the default value is 60s. Do you think this value must be increase or at least more easily configurable tru cli or removed and replace with a infinite value ? I didn't realise it could already be configured via settings.xml. It should be specifically called to attention in the docs and the release notes. An enhancement later could be to direct someone to an explanation in the error message. Last but not least do we have to consider this as blocker for the release ? Some way of addressing it (at a minimum clear docs) should be with the release. I would imagine this ending up causing complaints to repository manager user lists pretty quickly otherwise. Agree. I will add it in release and complete documentation here: http://maven.apache.org/guides/mini/guide-http-settings.html - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Agree. I will add it in release and complete documentation here: 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. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/12 Brian Fox bri...@infinity.nu: Agree. I will add it in release and complete documentation here: 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 br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
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 Foxbri...@infinity.nu: Agree. I will add it in release and complete documentation here: 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 br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
+1 to have it set to 5 or 10 minutes by default and with a big warning and associated doc in the release note 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: Agree. I will add it in release and complete documentation here: http://maven.apache.org/**guides/mini/guide-http-**settings.htmlhttp://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 br...@apache.org http://brettporter.wordpress.**com/http://brettporter.wordpress.com/ http://au.linkedin.com/in/**brettporterhttp://au.linkedin.com/in/brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Le 12 décembre 2011 16:21, Arnaud Héritier aherit...@gmail.com 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 i...@ifedorenko.com 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 Foxbri...@infinity.nu: Agree. I will add it in release and complete documentation here: http://maven.apache.org/**guides/mini/guide-http-**settings.htmlhttp://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 br...@apache.org http://brettporter.wordpress.**com/http://brettporter.wordpress.com/ http://au.linkedin.com/in/**brettporterhttp://au.linkedin.com/in/brettporter --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
On Mon, Dec 12, 2011 at 4:46 PM, Olivier Lamy ol...@apache.org wrote: Le 12 décembre 2011 16:21, Arnaud Héritier aherit...@gmail.com 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) ok associated doc in the release note Already prepared: http://maven.apache.org/docs/3.0.4/release-notes.html I propose to put the sentence a default read timeout configured to 60s. in blold. WDYT ? BTW I'm very happy to see some discussions here, I hope this release will be here one day :-) yes, we will succeed Users are waiting for it for 1 year now, thus 1 or 2 month more ... Arnaud
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
If we don't change things - the http settings guide should be updated, but also RELEASE NOTES for the new release should mention the change, and call it out. -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Tue, Dec 13, 2011 at 3:28 AM, Brian Fox bri...@infinity.nu wrote: Agree. I will add it in release and complete documentation here: 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. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I've noticed a potential problem when using a repository manager. The new wagon library seems to have introduced a read time out: Could not transfer artifact [...]: Read timed out - [Help 1] This is going to fail the first time you hit an artifact proxied by a repository manager that takes more than 1 minute to download because there is no progress on the read. In previous versions, there was only a connection timeout. I think that needs to be prevented, at least until the repository managers all stream proxied artifacts so there is some download progress to report. Cheers, Brett On 06/12/2011, at 1:28 AM, Olivier Lamy wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
+1 Tested it on several mojo-projects and non-java projects with customized default-lifecycle without any problem.I ran into MPIR-137[1] but that seems to be resolved with the fix for Dans issue. -Robert [1] https://jira.codehaus.org/browse/MPIR-237 From: ol...@apache.org Date: Wed, 7 Dec 2011 20:04:58 +0100 Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged To: dev@maven.apache.org Jesse, First huge thanks for your tests, that's very important for us to have feedbacks. But please note it's *not* an official release so this will never be distribute as an official Apache Maven release. It's only a rc build to get feedbacks from users. The staged repository will be deleted (at least the svn svn tags will be here). And after the defined testing period, an other build without the RC naming will be available for an official vote. Thanks again for your tests! 2011/12/7 Jesse Glick jesse.gl...@oracle.com: FYI - NetBeans nightly development builds [1] are now bundling RC3, to shake out problems in either the embedded APIs or general usage. [1] http://bits.netbeans.org/download/trunk/nightly/latest/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/8 Marvin Froeder velo...@gmail.com: Well, it was working already on 3.0.3 but when I moved to 3.0.4-RC I start getting missing poms warnings. The layout is declared inside my plugin and this plugin has extensionstrue on plugin configuration. I will try to create a reproducible case. Yes please. Because I cannot get that working with 3.0.3. VELO On Wed, Dec 7, 2011 at 9:15 PM, Olivier Lamy ol...@apache.org wrote: 2011/12/7 Marvin Froeder velo...@gmail.com: FWIW, 3.0.4-RC3 didn't worked with a custom repository layout Like http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/ I did not pin down the problem yet, but seems a regression from 3.0.3. How do you get that working with 3.0.3 ? How do you declare this new layout or where do you put the jar containing it with 3.0.3 ? On Mon, Dec 5, 2011 at 12:28 PM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Hello, i'm observing things like the following with a build: [INFO] Failsafe report directory: C:\workspace\nereus\nereus-web-it\target\failsafe-reports wagon http use multi threaded http connection manager maxPerRoute 20, max total 40 Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.pom 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:16 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:16 GMT 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.pom (4 KB at 5.4 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:18 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom (3 KB at 4.6 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.jar Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar (19 KB at 19.4 K B/sec) 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.jar (32 KB at 24.1 KB/sec) --- T E S T S xyz /cygdrive/c/workspace/ $ mvn --version Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100) Maven home: C:\prog\apache-maven-3.0.4-RC3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Programme\Java\jdk1.6.0_26\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows xyz /cygdrive/c/workspace/ $ Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058633.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Looks to be due to a cookie path not rewrite. Do you have a http frontend before your rpm ? If yes see http://markmail.org/message/djcagmgqg56zrlf4 2011/12/8 Karl Heinz Marbaise k...@soebes.de: Hello, i'm observing things like the following with a build: [INFO] Failsafe report directory: C:\workspace\nereus\nereus-web-it\target\failsafe-reports wagon http use multi threaded http connection manager maxPerRoute 20, max total 40 Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.pom 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:16 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:16 GMT 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.pom (4 KB at 5.4 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:18 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom (3 KB at 4.6 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.jar Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar (19 KB at 19.4 K B/sec) 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/surefire/surefire-testng/2.11/surefire-testng-2.11.jar (32 KB at 24.1 KB/sec) --- T E S T S xyz /cygdrive/c/workspace/ $ mvn --version Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100) Maven home: C:\prog\apache-maven-3.0.4-RC3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Programme\Java\jdk1.6.0_26\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows xyz /cygdrive/c/workspace/ $ Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058633.html Sent from the Maven Developers mailing list archive at
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Hi, Olivier Lamy wrote Looks to be due to a cookie path not rewrite. Do you have a http frontend before your rpm ? Hm...rpm ? I have downloaded the maven-3.0.4-RC3 from the stage site...and started my build mvn 3.0.4-RC3 instead of maven 3.0.3 and seeing those results... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058703.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/8 Karl Heinz Marbaise k...@soebes.de: Hi, Olivier Lamy wrote Looks to be due to a cookie path not rewrite. Do you have a http frontend before your rpm ? . Hm...rpm ? I mean Repository Manager :-) in your case looks nexus. So just check in case you have a http frontend, cookie path is correctly rewrite. BTW it's just a warning and doesn't prevent downloading the artifact I have downloaded the maven-3.0.4-RC3 from the stage site...and started my build mvn 3.0.4-RC3 instead of maven 3.0.3 and seeing those results... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058703.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Isn't it rather the actual contents of the Expires section of the header not being in English locale? Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT /James -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: 08 December 2011 12:53 To: Maven Developers List Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged Looks to be due to a cookie path not rewrite. Do you have a http frontend before your rpm ? If yes see http://markmail.org/message/djcagmgqg56zrlf4 2011/12/8 Karl Heinz Marbaise k...@soebes.de: Hello, i'm observing things like the following with a build: [INFO] Failsafe report directory: C:\workspace\nereus\nereus-web-it\target\failsafe-reports wagon http use multi threaded http connection manager maxPerRoute 20, max total 40 Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.pom 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:16 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:16 GMT 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.pom (4 KB at 5.4 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:18 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom (3 KB at 4.6 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.jar Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar (19 KB at 19.4 K B/sec) 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.jar (32 KB at 24.1 KB/sec) --- T E S T S xyz /cygdrive/c/workspace/ $ mvn --version Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100) Maven home: C:\prog\apache-maven-3.0.4-RC3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Programme\Java\jdk1.6.0_26\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/8 Nord, James jn...@nds.com: Isn't it rather the actual contents of the Expires section of the header not being in English locale? Yes looks to be a better explanation. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT /James -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: 08 December 2011 12:53 To: Maven Developers List Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged Looks to be due to a cookie path not rewrite. Do you have a http frontend before your rpm ? If yes see http://markmail.org/message/djcagmgqg56zrlf4 2011/12/8 Karl Heinz Marbaise k...@soebes.de: Hello, i'm observing things like the following with a build: [INFO] Failsafe report directory: C:\workspace\nereus\nereus-web-it\target\failsafe-reports wagon http use multi threaded http connection manager maxPerRoute 20, max total 40 Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.pom 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:16 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:16 GMT 08.12.2011 13:35:17 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.pom (4 KB at 5.4 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:17 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:17 GMT 08.12.2011 13:35:18 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07-Dez-2011 12:35:18 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.pom (3 KB at 4.6 KB/sec) Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.jar Downloading: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng-utils/2.11/surefire-testng-utils-2.11.jar (19 KB at 19.4 K B/sec) 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:18 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:18 GMT 08.12.2011 13:35:19 org.apache.maven.wagon.providers.http.httpclient.client.protocol.Respo nseProcessCookies processCookies WARNUNG: Invalid cookie header: Set-Cookie: rememberMe=deleteMe; Path=/nexus; Expires=Mi, 07-Dez-2011 12:35:19 GMT. Unable to parse expires attribute: Mi, 07- Dez-2011 12:35:19 GMT Downloaded: http://servername:8081/nexus/content/groups/public/org/apache/maven/su refire/surefire-testng/2.11/surefire-testng-2.11.jar (32 KB at 24.1 KB/sec) --- T E S T S xyz /cygdrive/c/workspace/ $ mvn --version Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100) Maven home: C:\prog\apache-maven-3.0.4-RC3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Programme\Java\jdk1.6.0_26\jre Default locale
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Hi Oliver, Olivier Lamy wrote I mean Repository Manager :-) in your case looks nexus. ;-) RPM has a different meaning for Redhat Package Manager thanks for the explanation... Olivier Lamy wrote So just check in case you have a http frontend, cookie path is correctly rewrite. BTW it's just a warning and doesn't prevent downloading the artifact I have rechecked that problem with a complete empty local repository with MVN 3.0.3 ...it does not produce a warning at all With mvn 3.0.4 RC3 it produces these warnings...for every artifact... I have a http frontend and the Nexus hasn't been changed for a long time (3 Months)... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058997.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Seems weird to me to get back expires returns in non en format. A sample: mbp-olamy:maven-plugins olamy$ curl -H Accept-Language: de -I http://www.google.de HTTP/1.1 200 OK Date: Thu, 08 Dec 2011 15:14:54 GMT Expires: -1 Cache-Control: private, max-age=0 Content-Type: text/html; charset=ISO-8859-1 Set-Cookie: expires=Sat, 07-Dec-2013 15:14:54 GMT; path=/; domain=.google.de ... So even asking de language, this is an en format. I wonder what is the locale used on your server to start the nexus instance. 2011/12/8 Karl Heinz Marbaise k...@soebes.de: Hi Oliver, Olivier Lamy wrote I mean Repository Manager :-) in your case looks nexus. ;-) RPM has a different meaning for Redhat Package Manager thanks for the explanation... Olivier Lamy wrote So just check in case you have a http frontend, cookie path is correctly rewrite. BTW it's just a warning and doesn't prevent downloading the artifact I have rechecked that problem with a complete empty local repository with MVN 3.0.3 ...it does not produce a warning at all With mvn 3.0.4 RC3 it produces these warnings...for every artifact... I have a http frontend and the Nexus hasn't been changed for a long time (3 Months)... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/CALL-FOR-TEST-Apache-Maven-3-0-4-RC3-staged-tp5048996p5058997.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I've tried it out on a few relatively tame builds...failsafe and dependency plugins being about the most exotic things tested. Everything looks like it's functioning well here. I'll try to take it out for a more aggressive test run today. On 12/5/11 9:28 AM, Olivier Lamy wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
FYI - NetBeans nightly development builds [1] are now bundling RC3, to shake out problems in either the embedded APIs or general usage. [1] http://bits.netbeans.org/download/trunk/nightly/latest/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Jesse, First huge thanks for your tests, that's very important for us to have feedbacks. But please note it's *not* an official release so this will never be distribute as an official Apache Maven release. It's only a rc build to get feedbacks from users. The staged repository will be deleted (at least the svn svn tags will be here). And after the defined testing period, an other build without the RC naming will be available for an official vote. Thanks again for your tests! 2011/12/7 Jesse Glick jesse.gl...@oracle.com: FYI - NetBeans nightly development builds [1] are now bundling RC3, to shake out problems in either the embedded APIs or general usage. [1] http://bits.netbeans.org/download/trunk/nightly/latest/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
FWIW, 3.0.4-RC3 didn't worked with a custom repository layout Like http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/ I did not pin down the problem yet, but seems a regression from 3.0.3. On Mon, Dec 5, 2011 at 12:28 PM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
2011/12/7 Marvin Froeder velo...@gmail.com: FWIW, 3.0.4-RC3 didn't worked with a custom repository layout Like http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/ I did not pin down the problem yet, but seems a regression from 3.0.3. How do you get that working with 3.0.3 ? How do you declare this new layout or where do you put the jar containing it with 3.0.3 ? On Mon, Dec 5, 2011 at 12:28 PM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
On 12/07/2011 02:04 PM, Olivier Lamy wrote: please note it's *not* an official release so this will never be distribute as an official Apache Maven release. It's only a rc build to get feedbacks from users. Yes of course. This is only temporary until another RC or a final build is published - sorry for not being clearer. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I'm +1ing this - have been doing releases all day without issue. Someone did make a comment about memory usage the other day, I am seeing OOM exceptions more often in my large reactor build under the RC, but that's mostly Rhino stuff that has an evil leak in it. I did see a Permgen in Javac yesterday but never saw it again strangeness. -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Tue, Dec 6, 2011 at 3:28 AM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I ran my current day-job nightmare. It showed the same failure of the assembly plugin to resolve a war dependency from the reactor that I see with 2.2.1 and 3.0.3, so that's all good. On Mon, Dec 5, 2011 at 9:28 AM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Look good to me, the issue reported by me for RC2 is fixed -Dan On Mon, Dec 5, 2011 at 6:28 AM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Tested on a couple of builds with mostly standard plugins, looks good. Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Dec 5, 2011 3:28 PM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
