Then we should work on to get a build out of the door.. if the core classes aren't changed anymore (at least we try)
We need something 'stable' or released now so that projects can build against these changes.
So all unit test that fail should be looked at as soon as possible


johan


Jonathan Locke wrote:


i refactored feedback message stuff and form validation. it's quite a bit simpler and better. apologies to those whose code i broke.
i can't think of anything else i want to change at this point. i think what's left to do is mainly documentation and bug fixing. does anyone have any major complaints about the core?




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to