On 6/9/06, Luke Taylor [EMAIL PROTECTED] wrote:
I'm not sure a release will be possible until Ben gets back from Europe.
There are always the nightly builds until then, if people need a quick fix.
Isn't it possible for someone else to roll a release? It's probably a
good time to contact Ben
I just locally changed my project.xml to use Spring 1.2.6 and 1.2.8. I
ran full test runs against both. Everything looks good.
The constructor signature for MockFilterConfig from spring-mock
changed which caused compilation failures with 1.2.8. That really only
effects the unit tests. I updated
Yeah, I grabbed a 1.1.0-SNAPSHOT yesterday and it seems to have solved several
issues we
were having. I recommend it to anyone who put 1.0-final in a production app...
do it now.
Not to be a snit, but I feel I should throw out -- for posterity's sake if
nothing else --
that that spring-2.0
Ray Krueger wrote:
OK so, 1.0.0 did not release well. The LDAP/Spring compatability
issue, and the NotSerializableException issue both warrant getting a
patch out asap I would think.
Unfortunately there hasn't been any talk about that. What's the plan here?
Yes... please!!!
b
Ben Munat wrote:
Ray Krueger wrote:
OK so, 1.0.0 did not release well. The LDAP/Spring compatability
issue, and the NotSerializableException issue both warrant getting a
patch out asap I would think.
Unfortunately there hasn't been any talk about that. What's the plan here?
