sebb wrote:
> There are quite a lot of assertions that don't give any details if a test
> fails.
>
> For example, the following currently fails when using Harmony:
>
> testIncreasingTolerance(org.apache.commons.math.ode.nonstiff.AdamsBashforthIntegratorTest)
> java.lang.AssertionError:
> a
I support either solution 1 or 2 from first section of solutions:
1- We will not be waiting for others till they decide whether donate
the code or not.
2- We will get more benefit for ASF as we may gain more committer to
join the community and help grow it more.
3- For the non-committers contrib
There are quite a lot of assertions that don't give any details if a test fails.
For example, the following currently fails when using Harmony:
testIncreasingTolerance(org.apache.commons.math.ode.nonstiff.AdamsBashforthIntegratorTest)
java.lang.AssertionError:
at org.junit.Assert.fail(Ass
Everyone, I think it is time again to reopen the discussions around
creating a Validator2 release [1], which implements the upcoming JSR-303
Bean Validation spec [2] and [3]. Since JSR-303 is now a required
component of Java EE 6 application servers and must be supported by
JSR-314 JSF2 and JS
On 04/09/2009, Luc Maisonobe wrote:
> Luc Maisonobe a écrit :
>
> > sebb a écrit :
> >> The ComplexFormat parse method allows spaces in Complex numbers, for
> >> example the following test case works fine:
> >>
> >> public void testParseSimpleNoDecimals2() {
> >> String source = "
Luc Maisonobe a écrit :
> sebb a écrit :
>> The ComplexFormat parse method allows spaces in Complex numbers, for
>> example the following test case works fine:
>>
>> public void testParseSimpleNoDecimals2() {
>> String source = "1 1 2 + 1i";
>> Complex expected = new Complex(112
