Re: [math] MersenneTwister question

My apologies, I was looking at the original c code and neglected to notice the cast. On Mon, Aug 29, 2011 at 12:56 AM, Greg Sterijevski gsterijev...@gmail.comwrote: Yes, you seem to have a good point. My bad. On Mon, Aug 29, 2011 at 12:50 AM, Ted Dunning ted.dunn...@gmail.comwrote: Why?

Re: [VOTE] Release Commons Configuration 1.7 based on RC1

On 8/28/11 11:53 AM, Oliver Heger wrote: Am 28.08.2011 20:08, schrieb Gary Gregory: +1 to removing the ant build. Gary The ant build files were generated using the maven-ant-plugin. The whole stuff looks pretty complicated, and I do not like the way it handles dependencies either. To make

Re: [math] Consistent use of ExceptionContext [was using the ExceptionContext facility]

Hello everyone, Looking at the present hierarchy of exceptions, I've had some further thoughts, actually supporting the use of context rather than property getters. Sticking with the same example, we have two exceptions - NonPositiveDefiniteMatrixException: already implemented -

Re: [VOTE] Release Commons Configuration 1.7 based on RC1

Am 29.08.2011 08:21, schrieb Phil Steitz: On 8/28/11 11:53 AM, Oliver Heger wrote: Am 28.08.2011 20:08, schrieb Gary Gregory: +1 to removing the ant build. Gary The ant build files were generated using the maven-ant-plugin. The whole stuff looks pretty complicated, and I do not like the way

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This

[ognl] Struts Issue

Hello guys, a discussion on the STruts list brought this to my attention: https://issues.apache.org/jira/browse/WW-3580 As Struts is one of OGNL main consumers, maybe we make them a little gift with OGNL 4.0. What do you think? Cheers Christian

Re: [math] Consistent use of ExceptionContext [was using the ExceptionContext facility]

On 8/28/11 11:56 PM, Sébastien Brisard wrote: Hello everyone, Looking at the present hierarchy of exceptions, I've had some further thoughts, actually supporting the use of context rather than property getters. Sticking with the same example, we have two exceptions -

Re: [ognl] Struts Issue

definitively +1, I didn't understand anyway how to fix OGNL, I personally need more time of investigation, so anyone else can feel free to fix if already knows the solution. I think we should fill an Issue also on OGNL space on Jira, WDYT? Many thanks in advance and thanks for notifying!!! All the

Re: [VOTE] Release Commons Configuration 1.7 based on RC1

Am 28.08.2011 21:44, schrieb Phil Steitz: [snip] I now see how the maven 1.4 profile excludes the classes requiring 1.5. As you suggest, it would be good to add a note on this to the release notes. IIUC what is going on, the classes excluded from compilation should also be excluded from the

[functor] New summarize component

Hi everyone, I'm sending this message as I was suggested to do so following this issue https://issues.apache.org/jira/browse/SANDBOX-340 opened in JIRA. I have basically submitted this initially to Commons Lang but that wasn't the right place for it and it was suggested instead I use this

Re: [math] Consistent use of ExceptionContext [was using the ExceptionContext facility]

Yes. Multiple scenarios can lead to the same exception, and context seems to be a very flexible feature for this kind of situations. However, as you said, this should be invoked as last resort. Context elements we are dead sure will always be passed to the exception should be implemented as

Re: [functor] New summarize component

Hi Liviu! nice to hear news for [functor] and thanks for the reminder; no needs to copy'n'paste the jira log since, given the issue id, everybody is able to load the related page and read the original message ;) The right way to proceed is * checkin out the [functor] code[1]; * import your

Re: [chain][discuss] v2 upgrade - follow-up

Hi all guys, I just fixed the clirr report generation and deployed the chain2 site on my personal ASF space[1], in order we can discuss the patch that Elijah kindly provided. WDYT? It is IMHO acceptable in order to apply the modifications in /trunk. TIA, all the best!!! Simo [1]

Re: [functor] Method 'XXX' is not designed for extension

Hi Matthew, DI is indeed a critical mass that today can not be ignored and since Apache Commons provides by definition common reusable components, [functor] has to be able as well to be easily adapted in a context where DI is required. There is anyway a non trivial consideration: [functor] is a

Re: [chain][discuss] v2 upgrade - follow-up

I am curious about the change of normal collections to concurrent collections. Is there overhead with the concurrent stuff? Most of my context access is not multithreaded. On Mon, Aug 29, 2011 at 2:53 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I just fixed the clirr report

Re: [chain][discuss] v2 upgrade - follow-up

On Mon, Aug 29, 2011 at 2:53 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I just fixed the clirr report generation and deployed the chain2 site on my personal ASF space[1], in order we can discuss the patch that Elijah kindly provided. WDYT? It is IMHO acceptable in order

Re: [functor] Method 'XXX' is not designed for extension

On Mon, Aug 29, 2011 at 3:17 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi Matthew, DI is indeed a critical mass that today can not be ignored and since Apache Commons provides by definition common reusable components, [functor] has to be able as well to be easily adapted in a context

Re: [chain][discuss] v2 upgrade - follow-up

Hi Simo, Before we look at releasing the changes (after a trunk merge), I think that we will need to update the documentation to include Generics and possibly change the unit tests to use Generics. That said - I'm cautious about changing the unit tests because they are verifying that the API