Dear all,
in this thread,
http://markmail.org/thread/hhvm6wv3d3uhkwqs
we had an interesting discussion on a bug which was revealed by
abstract unit tests on all implementations of RealVector. It turns out
that the bug is more far-reaching than we initially thought, and I
would like to make sure th
Hello,
2012/6/16 Sébastien Brisard :
> Hi Gilles,
> and thanks for your time spent on this issue!
>
> 2012/6/16 Gilles Sadowski :
>>> [...]
>>>
>>> >>
>>> >> > Maybe that we could also impose that it is forbidden to divide by a
>>> >> > sparse
>>> >> > vector whose default value is zero. This wil
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
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-graph has an issue affecting its community integration.
This issue
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-digester3 has an issue affecting its community integration.
This i
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-jxpath has an issue affecting its community integration.
This issu
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-math has an issue affecting its community integration.
This issue
On 17/06/2012 16:26, Phil Steitz wrote:
> On 6/17/12 1:13 AM, Mark Thomas wrote:
>> On 17/06/2012 08:49, Phil Steitz wrote:
>>> Looks like only the relatively trivial POOL-220 and POOL-217 affect
>>> 2.0.
>> +1
>>
>>> We need to resolve these and do some javadoc and site
>>> cleanup; but unless t
Hi Phil,
Le 17/06/2012 19:16, Phil Steitz a écrit :
> On 6/17/12 9:46 AM, Luc Maisonobe wrote:
>> Hi all,
>>
>> I recently encountered a cumbersome limitation with our current
>> UnivariateInterpolator interface. It is a simple interface that defines
>> only one method:
>>
>> public interface Un
Hi,
following up on the thread where we discussed about the current state
of the API [1], I want to discuss how to name the generic
RuntimeException we talked about. Here are some proposals:
1. BeanUtilsException
2. BeanUtilsReflectionException
3. ReflectionException
4. ReflectiveAcessException
On 6/17/12 9:46 AM, Luc Maisonobe wrote:
> Hi all,
>
> I recently encountered a cumbersome limitation with our current
> UnivariateInterpolator interface. It is a simple interface that defines
> only one method:
>
> public interface UnivariateInterpolator {
> UnivariateFunction interpolate(do
On Jun 17, 2012, at 7:42, sebb wrote:
> On 17 June 2012 03:40, Ralph Goers wrote:
>>
>> On Jun 16, 2012, at 2:26 PM, Gary Gregory wrote:
>>
>>> For now, I want @override so I am ok with 1.6 source but I is safe to
>>> the have 1.5 target? Commons-io >=2.3 is not pressing for VFS.
>>>
>>> Gary
>>
Hi all,
I recently encountered a cumbersome limitation with our current
UnivariateInterpolator interface. It is a simple interface that defines
only one method:
public interface UnivariateInterpolator {
UnivariateFunction interpolate(double xval[], double yval[]);
}
I needed three differ
On 6/17/12 1:13 AM, Mark Thomas wrote:
> On 17/06/2012 08:49, Phil Steitz wrote:
>> Looks like only the relatively trivial POOL-220 and POOL-217 affect
>> 2.0.
> +1
>
>> We need to resolve these and do some javadoc and site
>> cleanup; but unless there are other things we want to get into 2.0,
>>
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-exec-test has an issue affecting its community integration.
This i
On 17 June 2012 03:40, Ralph Goers wrote:
>
> On Jun 16, 2012, at 2:26 PM, Gary Gregory wrote:
>
>> For now, I want @override so I am ok with 1.6 source but I is safe to
>> the have 1.5 target? Commons-io >=2.3 is not pressing for VFS.
>>
>> Gary
>
> Why would it not be? If that is all you are doi
On 17 June 2012 08:51, wrote:
> sebb wrote:
>
>>On 16 June 2012 23:09, Mark Thomas wrote:
>>> On 16/06/2012 23:05, sebb wrote:
On 16 June 2012 22:35, Mark Thomas wrote:
> On 16/06/2012 22:33, sebb wrote:
>> On 16 June 2012 22:23, Gary Gregory
>>wrote:
>>> Did you update the c
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-jelly-tags-jmx has an issue affecting its community integration.
T
On 17/06/2012 08:49, Phil Steitz wrote:
> Looks like only the relatively trivial POOL-220 and POOL-217 affect
> 2.0.
+1
> We need to resolve these and do some javadoc and site
> cleanup; but unless there are other things we want to get into 2.0,
> I would like to move this toward a release. I
sebb wrote:
>The POOL download page
>http://commons.apache.org/pool/download_pool.cgi only has a link for
>1.6 (Java 1.5+) , although the dist/ area contains 1.6 and 1.5.7.
>
>Seems to me either the page should link to 1.5.7 (Java 1.3+) or the
>dist/ area should be tidied up.
>
>-
sebb wrote:
>On 16 June 2012 23:09, Mark Thomas wrote:
>> On 16/06/2012 23:05, sebb wrote:
>>> On 16 June 2012 22:35, Mark Thomas wrote:
On 16/06/2012 22:33, sebb wrote:
> On 16 June 2012 22:23, Gary Gregory
>wrote:
>> Did you update the changes.xml? Did I miss that?
>
> N
Looks like only the relatively trivial POOL-220 and POOL-217 affect
2.0. We need to resolve these and do some javadoc and site
cleanup; but unless there are other things we want to get into 2.0,
I would like to move this toward a release. I will volunteer to RM
if no one else wants to. Is there
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-scxml-test has an issue affecting its community integration.
This
23 matches
Mail list logo
