Oups, I meant Gary sorry... Dunno why I confused you with Craig... On Mon, Oct 20, 2008 at 12:17 PM, Simon Lessard <[EMAIL PROTECTED]>wrote:
> Hi Craig, > > The difference is the test framework, or at least a part of it, is linked > exclusively to JSF. More practically, what this mean is that we have a > cyclic reference between the API and the test. For example, the test > framework depends on FacesContext. However, since we like Shale test > framework, we also test the API with the framework, now this is a chicken or > egg issue. > > This is even more problematic in case of JSF 2.0 since there's no released > API to depend on, so I cannot modify the framework even by depending on > SNAPSHOT pseudo release since I cannot build those with unit test sicne > those unit tests aren't 2.0 compliant. I guess it would be possible to > create a pseudo release skipping unit tests, but it seems against the > standard quality reputation of Apache to do so. > > So, personally, I would have liked to put the JSF part of the framework in > MyFaces test project and release the test jar at the same time as the core > so that people can still use it as a dependency. > > > Regards, > > ~ Simon > > > On Mon, Oct 20, 2008 at 11:49 AM, Gary VanMatre <[EMAIL PROTECTED]>wrote: > >> >> -------------- Original message ---------------------- >> From: "Matthias Wessendorf" <[EMAIL PROTECTED]> >> > On Sun, Oct 19, 2008 at 11:34 PM, Kito Mann <[EMAIL PROTECTED]> >> wrote: >> > > Hey Simon, >> > > >> > > I don't think this has been officially decided. Check out the recent >> > > thread on this topic. >> > > >> > > However, if you're going to be making changes for JSF 2, this might be >> > > a good time to move it over to MyFaces. I don't think Gary agrees, >> > > though :-). >> > >> > I am also +1 on the move ;-) >> > >> >> Humm, well, I don't understand why shale test is excluded from the normal >> community protocol. For goodness sakes, what if every project felt it >> necessary to pull commons digester into their own just because they use it. >> >> I'd rather see the Shale community grow this library and the Shale >> project. However, if the communities feel that the only way we can find >> volunteers to contribute to its ongoing growth (seems a bit snobbish) is to >> move to MyFaces, then so be it. >> >> >> >> >> >> > > >> > > On Sun, Oct 19, 2008 at 1:04 PM, Simon Lessard >> > > <[EMAIL PROTECTED]> wrote: >> > >> Hi, >> > >> >> > >> I'm working on implementing JSF 2.0 for MyFaces and as you may know, >> MyFaces >> > >> uses Shale test for its unit testing. However, the new API and >> contracts >> > >> involved in JSF 2.0 make it so that current test fails with an >> > >> UnsupportedOperationException since some test implementations don't >> override >> > >> the new method that weren't marked abstract for binary code >> compatibility. >> > >> >> > >> Anyway, my point is, what is the current status and roadmap for >> shale-test >> > >> framework? Should JSF 2.0 changes be applied to it or will it be >> integrated >> > >> in in part or completely in MyFaces with time? >> > >> >> > >> >> > >> Thanks, >> > >> >> > >> ~ Simon >> > >> >> > > >> > > >> > > >> > > -- >> > > Kito D. Mann -- Author, JavaServer Faces in Action >> > > http://twitter.com/kito99 >> > > http://www.virtua.com - JSF/Java EE consulting, training, and >> mentoring >> > > http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info >> > > +1 203-404-4848 x3 >> > > >> > > * Sign up for the JSF Central newsletter! >> http://oi.vresp.com/?fid=ac048d0e17 >> > * >> > > >> > >> > >> > >> > -- >> > Matthias Wessendorf >> > >> > blog: http://matthiaswessendorf.wordpress.com/ >> > sessions: http://www.slideshare.net/mwessendorf >> > twitter: http://twitter.com/mwessendorf >> >> >
