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
[VOTE] Release Maven Release Plugin version 2.2.2
Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - 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: How to get nice doc for a bean-ie sort of Mojo parameter
Hi! It was great seeing that others have the same problem with complex objects for Maven configuration and the generated documentation. For the android maven plugin http://code.google.com/p/maven-android-plugin/ I have derived a bit of a standard on how we deal with this and we have implemented that approach for most of the plugin now. There is still more lingering to do but there is only so much time.. The android maven plugin defines a completely new lifecycle with lots of custom mojos and invocations and has a LOT of configuration options. We therefore decided to use the complex object approach. However that did not work nicely in terms of e.g. a complex object configuration in the plugin configuration then being overridden in the command line or with a property. So here is what we do - have a plain pojo with no annotations in the configuration package https://github.com/jayway/maven-android-plugin/tree/master/src/main/java/com/jayway/maven/plugins/android/configuration - use that as a configuration in the mojo e.g. the RunMojo https://github.com/jayway/maven-android-plugin/blob/master/src/main/java/com/jayway/maven/plugins/android/standalonemojos/RunMojo.java with the Run configuration object - then have another parameter for each one of the attributes of the configuration object. In the run case it is debug and the used parameter is runDebug which uses the expression android.run.debug and has a default value - then we have a resulting parameter called parsedDebug that is actually used in the execution - to derive it we parse the configuration by checking if there is a Run parameter (e.a. it is defined in the plugin config). if it is we use it but for each parameter we check if e.g. runDebug is defined and if so we let it over ride the parameter (therefore command line or property overrides plugin config). And then of course we get as much doc into it all as possible. Now while this is pretty ugly it works well enough and supports plugin configration, properties (in pom or setting) and command line properties as well and can produce a reasonable documentation.. sort of. I have also documented this a bit here http://code.google.com/p/maven-android-plugin/wiki/CodeConventions and I maintain the Android chapter in Maven: The Complete Reference and blog about things when I can to have more documentation.. I would love to hear your thoughts about this approach. manfred http://simpligility.com
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: Maven way of retrieving URL resources so that settings.xml/proxy is used?
On Tue, Dec 13, 2011 at 6:14 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: would mrm-maven-plugin help your integration tests? Is that Mock Repository Manager? Because the integration tests detect a real failure, unable to use URL resources behind a firewall, I need to solve it properly. Its just I happen to be behind a firewall so I notice this failure. - 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: Maven way of retrieving URL resources so that settings.xml/proxy is used?
well the primary issue that i required mrm-maven-plugin for was refusing the proxy settings of the invoking maven within the invoked maven. mrm-maven-plugin can be configured to serve all artifacts available and thus the @local-repo@ speedup can be used without having to seed the local repo with all required artifacts. if your issue is getting an artifact from somerandomurl that is not a GAV coordinate, then mrm-maven-plugin is not for you - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2011 20:20, Barrie Treloar baerr...@gmail.com wrote: On Tue, Dec 13, 2011 at 6:14 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: would mrm-maven-plugin help your integration tests? Is that Mock Repository Manager? Because the integration tests detect a real failure, unable to use URL resources behind a firewall, I need to solve it properly. Its just I happen to be behind a firewall so I notice this failure. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release Plugin version 2.2.2
hmm some strangeness with site:stage-deploy but the content can be found if you dig down ;-) +1 from me btw - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2011 17:20, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site
Re: Maven way of retrieving URL resources so that settings.xml/proxy is used?
On Wed, Dec 14, 2011 at 7:09 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: well the primary issue that i required mrm-maven-plugin for was refusing the proxy settings of the invoking maven within the invoked maven. mrm-maven-plugin can be configured to serve all artifacts available and thus the @local-repo@ speedup can be used without having to seed the local repo with all required artifacts. This looks interesting. Maven Eclipse Plugin is a chainsaw mix of testing, as it was early in the lifecycle of integration testing efforts. It takes ~7 minutes to complete on my 3+ year laptop. I'm interested in speeding that up. Do we have guides to walk me through what is considered best practice for integration testing, repositories, etc? if your issue is getting an artifact from somerandomurl that is not a GAV coordinate, then mrm-maven-plugin is not for you Yup. Thanks. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
