Re: [ALL] How to handle static imports [was: Re: svn commit: r1441784 - /commons/sandbox/beanutils2/trunk/src/main/java/org/apache/commons/beanutils2/PropertyDescriptorsRegistry.java]

2013-02-05 Thread Benedikt Ritter
Hey, thanks for your feedback. It's interesting to see that there seem to be two opposing opinions: Some try to avoid static imports as much as possible, while others use them if it makes the code more fluent. I found the Matt's comment especially useful, for pointing out, that we (as developers

Re: [ALL] How to handle static imports [was: Re: svn commit: r1441784 - /commons/sandbox/beanutils2/trunk/src/main/java/org/apache/commons/beanutils2/PropertyDescriptorsRegistry.java]

2013-02-05 Thread Stephen Colebourne
FYI, the Project Lambda Streams code and JSR-310 in JDK 1.8 are both written with static imports in mind. Moreover, with support for static methods in interfaces being added, this is likely to increase as a pattern. Those facts may or may not affect decisions in commons. Stephen On 4 February

Re: svn commit: r1441784 - /commons/sandbox/beanutils2/trunk/src/main/java/org/apache/commons/beanutils2/PropertyDescriptorsRegistry.java

2013-02-05 Thread Simone Tripodi
Guten Tag, Bene, I personally try to avoid static imports. Especially when you come to a legacy code base IMHO it makes the code harder to understand. as BU2 user, would you write the following sentence on( testBean ).invoke( setBooleanProperty ).with( argument( new Boolean( false ) ) );

[Math] Moving on or not?

2013-02-05 Thread Gilles
Hi. In the thread about static import, Stephen noted that decisions on a component's evolution are dependent on whether the future of the Java language is taken into account, or not. A question on the same theme also arose after the presentation of Commons Math in FOSDEM 2013. If we assume

Re: svn commit: r1441784 - /commons/sandbox/beanutils2/trunk/src/main/java/org/apache/commons/beanutils2/PropertyDescriptorsRegistry.java

2013-02-05 Thread Benedikt Ritter
Hi Simo, 2013/2/5 Simone Tripodi simonetrip...@apache.org Guten Tag, Bene, I personally try to avoid static imports. Especially when you come to a legacy code base IMHO it makes the code harder to understand. as BU2 user, would you write the following sentence on( testBean

[vfs] New feature request: configurable socket timeout for HTTP and WebDAV in VFS

2013-02-05 Thread Jean-Marc Borer
Hello list members, We need to be able to specify socket timeouts in VFS for HTTP and WebDAV in our project so that request will no hang for ever in certain conditions. I have modified the sources of HttpFileSystemConfigBuilder and HttpClientFactory to be able to configure this in HttpClient.

Re: [vfs] New feature request: configurable socket timeout for HTTP and WebDAV in VFS

2013-02-05 Thread Mark Fortner
Just out of curiousity, is there a reason that socket timeouts shouldn't also apply to all file systems in general? Cheers, Mark On Tue, Feb 5, 2013 at 8:58 AM, Gary Gregory garydgreg...@gmail.com wrote: Sure, make sure you base you patch on the latest from trunk. Gary On Tue, Feb 5,

Re: [vfs] New feature request: configurable socket timeout for HTTP and WebDAV in VFS

2013-02-05 Thread Gary Gregory
On Tue, Feb 5, 2013 at 4:54 PM, Mark Fortner phidia...@gmail.com wrote: Just out of curiousity, is there a reason that socket timeouts shouldn't also apply to all file systems in general? How does a socket timeout make sense for a local file system, ZIP, and so on? Gary Cheers, Mark

Re: [vfs] New feature request: configurable socket timeout for HTTP and WebDAV in VFS

2013-02-05 Thread Mark Fortner
Perhaps not for local file systems, but I would imagine that any kind of distributed file system would have need of a socket timeout. Cheers, Mark On Tue, Feb 5, 2013 at 1:59 PM, Gary Gregory garydgreg...@gmail.com wrote: On Tue, Feb 5, 2013 at 4:54 PM, Mark Fortner phidia...@gmail.com

[DAEMON] Tagging 1.0.13

2013-02-05 Thread Mladen Turk
Hi, I plan to tag and push for a release Daemon 1.0.13 later today. We have some regression, or better to say an old problem which manifested with new version which requires a new release. The fix was already confirmed by Tomcat folks. Regards -- ^TM