Thats my memory as well - the main change being inheritance, plus a few bug
fixes and deprecations being removed. Personally I haven't tried out
inheritance, so I can't vouch for it - but releasing a beta might prompt a
wider audience to give it a go. The main hurdleIMO to people moving or
trying
True, but it is a start. I'm +1 on aiming for a 1.2 beta of
commons-validator to coincide roughly with a Struts 1.3 release. I've
wittled down the bug list to one real bug and it kinda has a patch for
it available.
Looking at the steps on our site [1], looks like the first step is
voting a
+1 to you being the release manager.
Niall
- Original Message -
From: Don Brown [EMAIL PROTECTED]
Sent: Monday, August 29, 2005 6:24 AM
True, but it is a start. I'm +1 on aiming for a 1.2 beta of
commons-validator to coincide roughly with a Struts 1.3 release. I've
wittled down the
I believe I applied the form inheritance patch back in early 2004, and
at the time we
were trying to get a stable version of Validator out for Struts 1.2.X
series and creating the
Branch seemed the thing to do. 1.2 is also the version that David
removed deprecated
methods so releasing 1.2
If I remember right, 1.2 (HEAD) includes form inheritance which wasn't
widely tested. Niall might
remember more details. I think releasing 1.2.0 from HEAD would be fine so
we don't have to go through the error prone process of maintaining two
branches. Thanks for picking up the Validator torch!
I'd like to get a release of commons-validator out the door, as Struts
1.3 would like to use some of its new bug fixes and features.
I'm pretty new to validator, so I'm not familar with its history. Any
reason we haven't released 1.2? In the past when I fixed bugs, folks
backported them to the
