Yeah I know. I don't mind using it as unstable, I just want the core to be stable. Under 1.1.1, the latest validateCompareTo is looking for ResourceLoader, and hence stops my project from loading.
The two components I want are validateCompareTo and schedule for now. >From what others have said, it sounds like schedule is getting close to becoming part of tomahawk. Tonight I'm going to try to rip the validate compare to out of myfaces and into my source tree to try to get it to work against 1.1.1. Hopefully schedule works in the 1.1.1 version (I see the code is in the sandbox.jar for 1.1.1) well. -Andrew On 2/23/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Hi Andrew always have in mind that the sandbox is sort of a Tomahawk > unstable ... > anything in there can get a major overhaul between versions and to the > worse might be pulled. > (although for most components it is very very unlikely) > > > > Andrew Robinson schrieb: > > I have a bit of a dilemma. I would like to have the stability of > > MyFaces 1.1.1, but I'd like to use some of the new Sandbox components > > (like validateCompareTo) which are not in the 1.1.1 release and seem > > to require the newest core of myfaces to work (validateCompareTo was > > throwing class and method not found errors when I tried using it on > > myfaces 1.1.1). > > > > In the SVN branch, I find I come across many errors. The last one was > > a bad one. About a week ago t:commandButton tried to treat the > > "action" property as a ValueBinding instead of a MethodBinding. > > > > Any idea on the next scheduled release? (rc or beta would be nice over > > source control updates). > > > > Thanks, > > Andrew > > > >
