[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

[GUMP@vmgump]: Project commons-configuration (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-configuration has an issue affecting its community integration. Th

[GUMP@vmgump]: Project commons-jexl-jexl-compat (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-jexl-jexl-compat has an issue affecting its community integration

[scxml-js] Re: ANN: StateCharts Interpretation and Optimization eNgine (SCION)

I'm sorry, I meant to prefix the previous email with an [scxml-js] tag. Please excuse this oversight. Jake On Wed, Nov 30, 2011 at 7:19 PM, Jacob Beard wrote: > Hi, > > I just wanted to quickly announce that I have been working on SCION, a > successor to scxml-js, and have published its initial

ANN: StateCharts Interpretation and Optimization eNgine (SCION)

Hi, I just wanted to quickly announce that I have been working on SCION, a successor to scxml-js, and have published its initial release. The following blog post describes the motivation for the rewrite: http://blog.echo-flow.com/2011/06/08/masters-thesis-update-2-new-statecharts-project/ I'm dev

Re: [JEXL] binary compatibility

On 30 November 2011 22:15, henrib wrote: > I've committed the fix on the 2.0 branch - tests are OK - and if 2.1 is ever > released, this will be needed. That's not quite the fix I had in mind, also I'm not sure it addresses all the issues. I'll apply my fix to the 2.0-API branch before too long

Re: [JEXL] binary compatibility

I've committed the fix on the 2.0 branch - tests are OK - and if 2.1 is ever released, this will be needed. -- View this message in context: http://apache-commons.680414.n4.nabble.com/JEXL-binary-compatibility-tp4114818p4125259.html Sent from the Commons - Dev mailing list archive at Nabble.com.

Re: [JEXL] binary compatibility

On 30 November 2011 21:47, henrib wrote: > If we go back to pre JEXL-83 fix (protected non final strict field + setter) > and deprecate those, we can attempt releasing as 2.1 ? I think that would get us almost there. I propose to fix the strict/lenient bug in the 2.0-API-COMPAT branch and do som

Re: [JEXL] binary compatibility

If we go back to pre JEXL-83 fix (protected non final strict field + setter) and deprecate those, we can attempt releasing as 2.1 ? -- View this message in context: http://apache-commons.680414.n4.nabble.com/JEXL-binary-compatibility-tp4114818p4125129.html Sent from the Commons - Dev mailing list

Re: [JEXL] binary compatibility

On 30 November 2011 17:11, henrib wrote: > > About Was: Dear #{p} Doe; Now: Dear ${p} Doe; > As stated, the issue was that preparing a deferred expression must always > return an immediate (even composite) expression. When preparing "Dear #{p} > ${name};" , the immediate ${name} will be evaluated

Re: [JEXL] binary compatibility

About Was: Dear #{p} Doe; Now: Dear ${p} Doe; As stated, the issue was that preparing a deferred expression must always return an immediate (even composite) expression. When preparing "Dear #{p} ${name};" , the immediate ${name} will be evaluated - 'name' is the set of variables - and the prepara

Re: [JEXL] binary compatibility

On 30 November 2011 15:34, henrib wrote: > About Test org.apache.commons.jexl2.UnifiedJEXLTest that failed, the code had > bugs and was fixed. > 1187458 Fri Oct 21 18:40:17 CEST 2011   henrib > Added getVariables method (similar to JexlEngine) to extract all references > variables from an UJEXL ex

[GUMP@vmgump]: Project commons-jexl-jexl-compat (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-jexl-jexl-compat has an issue affecting its community integration

Re: [JEXL] binary compatibility

About Test org.apache.commons.jexl2.UnifiedJEXLTest that failed, the code had bugs and was fixed. 1187458 Fri Oct 21 18:40:17 CEST 2011 henrib Added getVariables method (similar to JexlEngine) to extract all references variables from an UJEXL expression; Fixed issue where preparing a deferred ex

[vfs] bug: zip file is not being closed

Hi. (I tried to sign up to VFS Jira but it fails again and again on the captcha for some reason, so I post here.) I found a bug in vfs2: When you open an input stream of a zip entry inside a zip file, the zip file is kept locked even after closing the zip file object. Below is code to re

Re: [JEXL] binary compatibility

On 29 November 2011 16:30, sebb wrote: > On 28 November 2011 16:26, sebb wrote: >> On 28 November 2011 15:55, henrib wrote: >>> I added @since 2.1, renamed the Uberspect.getConstructor, removed final for >>> silent & strict in Interpreter (although Interpreter instances probably >>> never need t

Re: [CANCELLED] Release JEXL 3.0 based on RC1

On 30 November 2011 06:56, Luc Maisonobe wrote: > Le 29/11/2011 22:28, Matt Benson a écrit : >> On Tue, Nov 29, 2011 at 3:19 PM, Gary Gregory wrote: >>> On Tue, Nov 29, 2011 at 2:09 PM, Henri Biestro wrote: >>> I'm obviously unfit as RM. >>> >>> I do not think so. >> >> +1.  I've only

[math] add method pow(int) to FieldElement

Hello, I could use the method {{pow(int)}} in FieldElement. Browsing through the current implementation of CM, I can see this method already exists in some classes which implement FielElement: BigFraction, Complex (with Complex argument). I cannot write a default implementation, though, since Field

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

On 2011-11-30, James Carman wrote: > Is there a way to see the actual failure messages for this? lists all test reports at the bottom. > The TestXmlRpcInvoker test has been failing for quite some time. I > belie

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

Is there a way to see the actual failure messages for this? The TestXmlRpcInvoker test has been failing for quite some time. I believe it tries to set up a server socket on the machine if I remember correctly. Perhaps that's not allowed anymore or something? On Tue, Nov 29, 2011 at 1:05 AM, Gum