Hello Andy, Keep in mind that whatever workarounds are required for Shale Test will likely be required for MyFaces Test as well, so please make the solutions known (we're using MyFaces Test along with the Spring testing framework for a project). --- Kito D. Mann | twitter: kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter: jsfcentral +1 203-404-4848 x3
Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17 On Tue, Jul 13, 2010 at 12:22 PM, Andy Schwartz (JIRA) < [email protected]> wrote: > Remove dependency on Shale Test > ------------------------------- > > Key: TRINIDAD-1850 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1850 > Project: MyFaces Trinidad > Issue Type: Task > Reporter: Andy Schwartz > > > Trinidad's unit tests are based on Apache Shale Test, which is now a > retired project. Trinidad should cut over to MyFaces Test in order to avoid > the dependency on a project that is no longer being actively developed. > > Note that the Trinidad unit tests are currently failing when run against > Mojarra 2.0.3 due to incompatibilities between Shale Test and JSF 2.0. I am > working with the Mojarra team to see whether they can provide a workaround > for this particular issue. However, the current strategy of relying on > Shale Test is not an acceptable long-term solution. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
