the commit I did was a revert to ensure the backward comp. Sean opend a bug that there were issues with Tomahawk 113. I tested and figured out and did the revert
-Matthias On 9/15/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 9/15/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > there was something I changed to the branch in june/july to be able > to have 114 working with tomahawk 113. > Sean, you and I were discussing that. > > Now you say it's not working w/ core 114. > Why ? I think we were talking about getScrolling back then. That was a non-essential change that we could revert. I noticed this change when reading the commit messages, not by actual testing against 1.1.3. It sounds like there was another change that we didn't catch that was required to provide JSF RI compatibility, but also had to break 1.1.3 compatibility. ---------- Forwarded message ---------- From: Martin Marinschek <[EMAIL PROTECTED]> Date: Sep 11, 2006 12:32 PM Subject: Re: Release MyFaces Core 1.1.4 -- bug with datatable showing wrong # of lines To: MyFaces Development <[email protected]> [...] I saw that you guys renamed the getScrolling again. I wonder about the clear...xx method that I renamed as well, to comply with the RI's method. Thinking about this now, I believe this will mean we can't use implementation version 1.1.5 with tomahawk 1.1.3. This whole javascript thing is a problem - the interdependency between implementations and different components in the component libraries shows here clearly!
-- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
