OK, I've opened JEXL-69 for this:
https://issues.apache.org/jira/browse/JEXL-69
I probably won't get to it this week, so no assignee ATM.
-Rahul
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comm
On 03/08/2009, Rahul Akolkar wrote:
> On Mon, Aug 3, 2009 at 11:57 AM, sebb wrote:
> > There are some classes and methods which are now deprecated in 2.0.
> >
> > However, the deprecated items are still used by much of the test code.
> >
> > Seems to me that the test cases ought not to use de
Luc Maisonobe wrote:
> Jörg Schaible a écrit :
>> Hi Luc,
>>
>> Luc Maisonobe wrote:
>>
>>> Jörg Schaible a écrit :
Hi Luc,
Luc Maisonobe wrote:
> Jörg Schaible a écrit :
>> Hi Luc,
>>
[snip]
>> we're definitely on the right track. After changing the
On 03/08/2009, Rahul Akolkar wrote:
> IMO the following doesn't have much value and sticks out as the last
> non-standard (in the m2 sense) area in SVN:
>
> http://svn.apache.org/repos/asf/commons/proper/jexl/branches/2.0/examples/
>
> WDYT? Does it help you? :-)
Not really - it's quite diffi
Jörg Schaible a écrit :
> Hi Luc,
>
> Luc Maisonobe wrote:
>
>> Jörg Schaible a écrit :
>>> Hi Luc,
>>>
>>> Luc Maisonobe wrote:
>>>
Jörg Schaible a écrit :
> Hi Luc,
>
>>> [snip]
>>>
> we're definitely on the right track. After changing the loop in
> TestProblem3 the tests r
Hi Luc,
Luc Maisonobe wrote:
> Jörg Schaible a écrit :
>> Hi Luc,
>>
>> Luc Maisonobe wrote:
>>
>>> Jörg Schaible a écrit :
Hi Luc,
>> [snip]
>>
we're definitely on the right track. After changing the loop in
TestProblem3 the tests run through. However, now I have two faili
I agree; turning them both as unit tests not for their intrinsic testing
value but just as usage example that we can link the doc to would be nice.
Which might be a good way to present other use-cases as well (extending
JexlArithmetic, Interpreter, UnifiedJEXL and XML...).
--
View this message
Phil Steitz wrote:
> Jörg Schaible wrote:
>> Hi Phil,
>>
>> Phil Steitz wrote:
>>
>>
>>> Luc Maisonobe wrote:
>>>
Jörg Schaible a écrit :
> Hi Phil,
[snip]
>>> Fine by me, though it is annoying that we are forced to do this.
>>>
>>
>> Well, y
Rahul Akolkar wrote:
>
> On Mon, Aug 3, 2009 at 1:30 PM, Henrib wrote:
>>
>>
>> The tests use the ExpressionFactory & ScriptFactory a lot indeed; using a
>> static JexlEngine in those test classes should be equivalent.
>> I can refactor these if this helps and I'm not stepping on anyone's toes.
IMO the following doesn't have much value and sticks out as the last
non-standard (in the m2 sense) area in SVN:
http://svn.apache.org/repos/asf/commons/proper/jexl/branches/2.0/examples/
WDYT? Does it help you? :-)
These could be turned into unit tests instead (that'll keep them upto
date as
On Mon, Aug 3, 2009 at 1:30 PM, Henrib wrote:
>
>
> The tests use the ExpressionFactory & ScriptFactory a lot indeed; using a
> static JexlEngine in those test classes should be equivalent.
> I can refactor these if this helps and I'm not stepping on anyone's toes.
That'd be great.
-Rahul
-
On Mon, Aug 3, 2009 at 11:57 AM, sebb wrote:
> There are some classes and methods which are now deprecated in 2.0.
>
> However, the deprecated items are still used by much of the test code.
>
> Seems to me that the test cases ought not to use deprecated classes
> and methods unless the test is actu
On Mon, Aug 3, 2009 at 12:10 PM, wrote:
> Author: sebb
> Date: Mon Aug 3 16:10:25 2009
> New Revision: 800447
>
> URL: http://svn.apache.org/viewvc?rev=800447&view=rev
> Log:
> Give scripts access to a logger
>
> Modified:
>
> commons/proper/jexl/branches/2.0/src/main/java/org/apache/commons/
The tests use the ExpressionFactory & ScriptFactory a lot indeed; using a
static JexlEngine in those test classes should be equivalent.
I can refactor these if this helps and I'm not stepping on anyone's toes.
--
View this message in context:
http://www.nabble.com/-JEXL--Handling-of-deprecated-
There are some classes and methods which are now deprecated in 2.0.
However, the deprecated items are still used by much of the test code.
Seems to me that the test cases ought not to use deprecated classes
and methods unless the test is actually for testing the item.
Any views on this?
---
- "Niall Pemberton" a écrit :
> I have prepared a third release candidate for Codec 1.4 following the
> feedback from the first.
>
> [ ] +1 Yes go ahead an release based on RC3
+1
Luc
> [ ] -1 No, because...
>
> The tag for RC3 is here:
> http://svn.apache.org/viewvc/commons/proper/code
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-jaxme has an issue affecting its community
integration
- "Phil Steitz" a écrit :
> Distributions are here:
> http://people.apache.org/~psteitz/commons-math-2.0-RC4/
>
> Tag is here:
> http://svn.apache.org/repos/asf/commons/proper/math/tags/MATH_2_0_RC4/
>
> To reduce the size of the binary distribution and to eliminate broken
>
> links in th
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-fmt-test has an issue affecting its community
integrat
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-configuration-test has an issue affecting its community
integrati
On Mon, Aug 3, 2009 at 9:52 AM, Gary
Gregory wrote:
>
>
>> -Original Message-
>> From: Phil Steitz [mailto:phil.ste...@gmail.com]
>> Sent: Sunday, August 02, 2009 6:19 PM
>> To: Commons Developers List
>> Subject: Re: [VOTE] Release Codec 1.4 based on RC3
>>
>> Niall Pemberton wrote:
>> > I
> -Original Message-
> From: Phil Steitz [mailto:phil.ste...@gmail.com]
> Sent: Sunday, August 02, 2009 6:19 PM
> To: Commons Developers List
> Subject: Re: [VOTE] Release Codec 1.4 based on RC3
>
> Niall Pemberton wrote:
> > I have prepared a third release candidate for Codec 1.4 follow
> -Original Message-
> From: Phil Steitz [mailto:phil.ste...@gmail.com]
> Sent: Sunday, August 02, 2009 6:19 PM
> To: Commons Developers List
> Subject: Re: [VOTE] Release Codec 1.4 based on RC3
>
> Niall Pemberton wrote:
> > I have prepared a third release candidate for Codec 1.4 followin
23 matches
Mail list logo
