On Tue, Jan 08, 2013 at 04:14:03PM +0530, Kishan Kavala wrote: > Ilia Shakitko, > I changed the fix version for this bug to 4.1. We should definitely fix > this for 4.1.
Any reason we can't put this in 4.0.1 as well? It looks like this was a regression from 3.0.x -> 4.0.0-incubating. Best, jzb -- Joe Brockmeier http://dissociatedpress.net/ Twitter: @jzb
