+1 It wasted some time for me; I used the work around, but ultimately decided to revert to 2.2.6.
___ Kito D. Mann | @kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com | @jsfcentral +1 203-998-0403 * Listen to the Enterprise Java Newscast: *http:// <http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com <http://ww.enterprisejavanews.com>* * JSFCentral Interviews Podcast: http://www.jsfcentral.com/resources/jsfcentralpodcasts/ * Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17 On Fri, Mar 27, 2015 at 3:46 AM, Dennis Kieselhorst <[email protected]> wrote: > Hi, > > I suggest to do a 2.2.8 release soon. Although there is a workaround for > MYFACES-3948, several devs told me that latest MyFaces release is unusable > for them. And everybody who is not aware of that issue spends time in > analyzing and fixing it. We already have five duplicates. > > Cheers > Dennis > > > > -- > View this message in context: > http://myfaces.10567.n7.nabble.com/MyFaces-2-2-8-release-tp119589.html > Sent from the My Faces - Dev mailing list archive at Nabble.com. >
