Re: 1.2.0 Resurrected

[Ted Husted]

If the Validation 1.1.1 release is imminent, the best thing might be to 
just let that be the Struts 1.2.0 trigger. If it happens a few days 
later, then so be it. As it stands, TC3 is our 2.2/1.2 benchmark, and we 
don't want to start cutting corners.

Of course, if anyone wanted to step up to bat and cut a Validator 1.1.1 
while Rob was on holiday, I'm sure he wouldn't mind :) It's a commons 
product, so any Jakarta Committer is eligible to join in the fun!

As for 1.2.0 testing, I would suggest we do TC 3.3.1a and 4.1.28, since 
they are the reference implementations for the reigning specifications.

-Ted.

Robert Leland wrote:
The Validator 1.1.0 has a bug that shows up a fatal bug in TC 3.X but 
not in 4.X....
Agreed, go ahead and use c-v 1.1.0, though if no one objects I'll do a 
release of validator and
if it comes out in time you have the option of using that instead.

The only stumbling block now is that I need to change my public key to 
use stronger
encryption so Martin doesn't get a 'warning' from my signed files.

-Rob


-T.

Robert Leland wrote:





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
Ted Husted,
  Junit in Action  - <http://www.manning.com/massol/>,
  Struts in Action - <http://husted.com/struts/book.html>,
  JSP Site Design  - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]