Sigh. Yes another branch is probably best. The other option is to create a branch for the JSF 1.1 release and hope that we don't need it. That might be better because at this late stage we may get lucky and not need to fix anything in shared. Even if we do fix things for the 1.1 core there will probably be way more changes for 1.2 so merging might be less confusing this way.
Also, I think the version of shared should be upgraded so we are not confused. Maybe 3.0.0? Sean On 6/5/06, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Yeah, another branch there, sure. regards, Martin On 6/5/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > Yeah, > > I also had an issue w/ the shared trunk by introducing autocomplete to > h:inputText (in 1.2) Also I integrated autocomplete to t:inputText. At > wasn't possible to use shared's base tags. since then... the base tag > has a "setAutocomplete()". > > In JSF 1.1 this is wrong. Some containers compate tld attributes and > setters on the tag clazz. > > So no chance to *enhance* the base clazz. I added it to impl inputtext tag class > > so... it looks to me for a branch here too ? > > > On 6/5/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > > The 1.2 impl project depends on shared 2.0.2-SNAPSHOT . There is some work I'd like to commit on a few issues but such changes mean shared trunk could never be used for a 1.1 bug fix release. Thoughts? > > > > Dennis Byrne > > > > > > > > > -- > Matthias Wessendorf > Aechterhoek 18 > 48282 Emsdetten > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
