Re: Use 1.2 as current
+1 to use 1.2 as trunk because I believe it'll speed up the development. Also +1 to Manfred's suggestion. Regards, Cagatay
RE: Use 1.2 as current now
Thanks. I just want to make sure I have my story correct - I'm often training people who are using MyFaces and asking about 1.2 J. ~~~ Kito D. Mann - Author, JavaServer Faces in Action <http://www.JSFCentral.com> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info * Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 * From: Zubin Wadia [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 10:27 AM To: MyFaces Development; [EMAIL PROTECTED] Subject: Re: Use 1.2 as current now Kito, Here are the current unassigned issues as per Martin Haimberger's report to the list previously: MYFACES-1563 - Christoph will do that. MYFACES-1255 - Crosschecked with RI -> Only javadoc MYFACES-1264 - Christoph will do that. MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification MYFACES-1204 - Martin (me) will check this. MYFACES-1236 - This issues is open. MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1217 - Implemented christoph will recheck this. MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1434 - Martin (me) will do "Add element "deferred-value/method" for elements in the taglibs" MYFACES-1444 - patch available MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is not compatible with the JSF 1.2 specification. Could be done for t:dataTable MYFACES-1548 - patch available MYFACES-1564 - Christoph Ebner will do that. MYFACES-1220 - This issue is open. MYFACES-1221 - Martin (me) will test this with an own renderkit. MYFACES-1230 - Specification Request, someone should recheck this. MYFACES-1582 - patch available MYFACES-1584 - patch available MYFACES-1223 - low priority Cheers, Zubin. On 4/18/07, Kito D. Mann <[EMAIL PROTECTED]> wrote: Martin, How complete is the work on 1.2? ~~~ Kito D. Mann ([EMAIL PROTECTED]) Author, JavaServer Faces in Action http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info > -Original Message- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 18, 2007 4:07 AM > To: MyFaces Development > Subject: Use 1.2 as current now > > Hi *, > > I wonder if we should switch the trunk to be the 1.2 branch now, cause > our next release will surely be fully 1.2 compatible (Tomcat 6 is out > now, so the sooner we're done, the better)... We'll have a lot better > testing of 1.2 if we do it like this - wdyt? > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces
Re: Use 1.2 as current
+1 for making 1.2 current. +1 for Manfred's structure. Once things have settled down (after Martin's attempted/successful merge), I'm going to do another source code audit to ensure the licensing is all compliant. On 4/18/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Manfred's idea sounds good to me. I especially appreciate that it will cause minimal disruption. Best wishes, Paul On Apr 18, 2007, at 7:21 AM, Manfred Geiler wrote: > Yes. > +1 for a switch > > But let's discuss the "how" first. > > Just had a look at the tomcat repo and I like the structure they use. > Main issue is that they do not name their trunk folder "trunk" but > rather give it a name corresponding to the actual major/minor version > (eg "tc5.5.x"). I like this idea. > And what is more: moving the current trunk to branches sounds weird to > me. The 1.1.x is no branch and never will be a real branch of 1.2.x. > So, why force it into the branches folder? MyFaces 1.1.x and MyFaces > 1.2.x have more the nature of two separate development trunks because > they implement different specs. The Tomcat guys address such issues in > the way I just described. So, why not learn from them? > > So, if we follow that path consistently our (sub)projects will each > have the following structure: > > /branches > /branches/1_1_6 > /branches/1_2_1 > /tags > /tags/1_1_2 > /tags/1_1_3 > /tags/1_1_4 > /tags/1_1_5 > /tags/1_2_0 > /tags/1_2_1 > /1_1_x <--- the trunk for JSF 1.1 development > /1_2_x <--- the trunk for JSF 1.2 development > > The great advantage: We can do this step by step without breaking > anything. All we need to do is point the externals in the "current" > project to the right trunk folder. We even can do the restructuring > first and point the externals to the corresponding "1_1_x" trunks and > in a second step switch "current" to the "1_2_x" trunks without a need > to restructure again. > > WDYT? > > --Manfred > > > > On 4/18/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: >> +1 but without a merge of the 1.1 trunk into 1.2. We have to select >> each individual issue. That is quite time consuming and shouldn't be >> done with this step. >> >> What about this: >> move current trunk to a 1.1 branch and >> move current 1.2 branch to trunk. >> >> That is quite a small step without any side effects to the >> existing code base. >> >> Cheers, >> Mathias >> >> 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: >> > Hi *, >> > >> > this is a formal vote on using the 1.2 branch as current now. >> > >> > Steps in doing this: >> > >> > - branch the current head as 1.1.5_1 >> > - merge down the 1.2 branch to current head (that will be a lot of >> > work, I'll tackle it) >> > >> > my +1 for doing this right now. >> > >> > regards, >> > >> > Martin >> > >> > -- >> > >> > http://www.irian.at >> > >> > Your JSF powerhouse - >> > JSF Consulting, Development and >> > Courses in English and German >> > >> > Professional Support for Apache MyFaces >> > >> > > > -- > http://www.irian.at > Your JSF powerhouse - JSF Consulting, > Development and Courses in English and > German > > Professional Support for Apache MyFaces -- Grant Smith
Re: Use 1.2 as current
Manfred addressed my concerns that I just posted on the other thread. +1 On 4/18/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Manfred's idea sounds good to me. I especially appreciate that it will cause minimal disruption. Best wishes, Paul On Apr 18, 2007, at 7:21 AM, Manfred Geiler wrote: > Yes. > +1 for a switch > > But let's discuss the "how" first. > > Just had a look at the tomcat repo and I like the structure they use. > Main issue is that they do not name their trunk folder "trunk" but > rather give it a name corresponding to the actual major/minor version > (eg "tc5.5.x"). I like this idea. > And what is more: moving the current trunk to branches sounds weird to > me. The 1.1.x is no branch and never will be a real branch of 1.2.x. > So, why force it into the branches folder? MyFaces 1.1.x and MyFaces > 1.2.x have more the nature of two separate development trunks because > they implement different specs. The Tomcat guys address such issues in > the way I just described. So, why not learn from them? > > So, if we follow that path consistently our (sub)projects will each > have the following structure: > > /branches > /branches/1_1_6 > /branches/1_2_1 > /tags > /tags/1_1_2 > /tags/1_1_3 > /tags/1_1_4 > /tags/1_1_5 > /tags/1_2_0 > /tags/1_2_1 > /1_1_x <--- the trunk for JSF 1.1 development > /1_2_x <--- the trunk for JSF 1.2 development > > The great advantage: We can do this step by step without breaking > anything. All we need to do is point the externals in the "current" > project to the right trunk folder. We even can do the restructuring > first and point the externals to the corresponding "1_1_x" trunks and > in a second step switch "current" to the "1_2_x" trunks without a need > to restructure again. > > WDYT? > > --Manfred > > > > On 4/18/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: >> +1 but without a merge of the 1.1 trunk into 1.2. We have to select >> each individual issue. That is quite time consuming and shouldn't be >> done with this step. >> >> What about this: >> move current trunk to a 1.1 branch and >> move current 1.2 branch to trunk. >> >> That is quite a small step without any side effects to the >> existing code base. >> >> Cheers, >> Mathias >> >> 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: >> > Hi *, >> > >> > this is a formal vote on using the 1.2 branch as current now. >> > >> > Steps in doing this: >> > >> > - branch the current head as 1.1.5_1 >> > - merge down the 1.2 branch to current head (that will be a lot of >> > work, I'll tackle it) >> > >> > my +1 for doing this right now. >> > >> > regards, >> > >> > Martin >> > >> > -- >> > >> > http://www.irian.at >> > >> > Your JSF powerhouse - >> > JSF Consulting, Development and >> > Courses in English and German >> > >> > Professional Support for Apache MyFaces >> > >> > > > -- > http://www.irian.at > Your JSF powerhouse - JSF Consulting, > Development and Courses in English and > German > > Professional Support for Apache MyFaces
Re: Use 1.2 as current now
Will there be a clear process in place for those who are not using 1.2 yet to check and out and fix 1.1 issues? There's 80+ issues still open. My initial reaction was -1, but I'm tending more toward +1 now, so long as 1.1 development can continue fairly easily. I'm hoping to be able to switch to Java 1.5 in a month or two, but that's not yet an option. On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current now
based on the TCK rules, we can only say, MyFaces hasn't passed it yet. On 4/18/07, Kito D. Mann <[EMAIL PROTECTED]> wrote: Martin, How complete is the work on 1.2? ~~~ Kito D. Mann ([EMAIL PROTECTED]) Author, JavaServer Faces in Action http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info > -Original Message- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 18, 2007 4:07 AM > To: MyFaces Development > Subject: Use 1.2 as current now > > Hi *, > > I wonder if we should switch the trunk to be the 1.2 branch now, cause > our next release will surely be fully 1.2 compatible (Tomcat 6 is out > now, so the sooner we're done, the better)... We'll have a lot better > testing of 1.2 if we do it like this - wdyt? > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Use 1.2 as current now
Kito, Here are the current unassigned issues as per Martin Haimberger's report to the list previously: MYFACES-1563 - Christoph will do that. MYFACES-1255 - Crosschecked with RI -> Only javadoc MYFACES-1264 - Christoph will do that. MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification MYFACES-1204 - Martin (me) will check this. MYFACES-1236 - This issues is open. MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1217 - Implemented christoph will recheck this. MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1434 - Martin (me) will do "Add element "deferred-value/method" for elements in the taglibs" MYFACES-1444 - patch available MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is not compatible with the JSF 1.2 specification. Could be done for t:dataTable MYFACES-1548 - patch available MYFACES-1564 - Christoph Ebner will do that. MYFACES-1220 - This issue is open. MYFACES-1221 - Martin (me) will test this with an own renderkit. MYFACES-1230 - Specification Request, someone should recheck this. MYFACES-1582 - patch available MYFACES-1584 - patch available MYFACES-1223 - low priority Cheers, Zubin. On 4/18/07, Kito D. Mann <[EMAIL PROTECTED]> wrote: Martin, How complete is the work on 1.2? ~~~ Kito D. Mann ([EMAIL PROTECTED]) Author, JavaServer Faces in Action http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info > -Original Message- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 18, 2007 4:07 AM > To: MyFaces Development > Subject: Use 1.2 as current now > > Hi *, > > I wonder if we should switch the trunk to be the 1.2 branch now, cause > our next release will surely be fully 1.2 compatible (Tomcat 6 is out > now, so the sooner we're done, the better)... We'll have a lot better > testing of 1.2 if we do it like this - wdyt? > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces
RE: Use 1.2 as current now
Martin, How complete is the work on 1.2? ~~~ Kito D. Mann ([EMAIL PROTECTED]) Author, JavaServer Faces in Action http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info > -Original Message- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 18, 2007 4:07 AM > To: MyFaces Development > Subject: Use 1.2 as current now > > Hi *, > > I wonder if we should switch the trunk to be the 1.2 branch now, cause > our next release will surely be fully 1.2 compatible (Tomcat 6 is out > now, so the sooner we're done, the better)... We'll have a lot better > testing of 1.2 if we do it like this - wdyt? > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces
Re: Use 1.2 as current
Manfred's idea sounds good to me. I especially appreciate that it will cause minimal disruption. Best wishes, Paul On Apr 18, 2007, at 7:21 AM, Manfred Geiler wrote: Yes. +1 for a switch But let's discuss the "how" first. Just had a look at the tomcat repo and I like the structure they use. Main issue is that they do not name their trunk folder "trunk" but rather give it a name corresponding to the actual major/minor version (eg "tc5.5.x"). I like this idea. And what is more: moving the current trunk to branches sounds weird to me. The 1.1.x is no branch and never will be a real branch of 1.2.x. So, why force it into the branches folder? MyFaces 1.1.x and MyFaces 1.2.x have more the nature of two separate development trunks because they implement different specs. The Tomcat guys address such issues in the way I just described. So, why not learn from them? So, if we follow that path consistently our (sub)projects will each have the following structure: /branches /branches/1_1_6 /branches/1_2_1 /tags /tags/1_1_2 /tags/1_1_3 /tags/1_1_4 /tags/1_1_5 /tags/1_2_0 /tags/1_2_1 /1_1_x <--- the trunk for JSF 1.1 development /1_2_x <--- the trunk for JSF 1.2 development The great advantage: We can do this step by step without breaking anything. All we need to do is point the externals in the "current" project to the right trunk folder. We even can do the restructuring first and point the externals to the corresponding "1_1_x" trunks and in a second step switch "current" to the "1_2_x" trunks without a need to restructure again. WDYT? --Manfred On 4/18/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: +1 but without a merge of the 1.1 trunk into 1.2. We have to select each individual issue. That is quite time consuming and shouldn't be done with this step. What about this: move current trunk to a 1.1 branch and move current 1.2 branch to trunk. That is quite a small step without any side effects to the existing code base. Cheers, Mathias 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: > Hi *, > > this is a formal vote on using the 1.2 branch as current now. > > Steps in doing this: > > - branch the current head as 1.1.5_1 > - merge down the 1.2 branch to current head (that will be a lot of > work, I'll tackle it) > > my +1 for doing this right now. > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current
+1 for Manfreds suggestion. 2007/4/18, Manfred Geiler <[EMAIL PROTECTED]>: Yes. +1 for a switch But let's discuss the "how" first. Just had a look at the tomcat repo and I like the structure they use. Main issue is that they do not name their trunk folder "trunk" but rather give it a name corresponding to the actual major/minor version (eg "tc5.5.x"). I like this idea. And what is more: moving the current trunk to branches sounds weird to me. The 1.1.x is no branch and never will be a real branch of 1.2.x. So, why force it into the branches folder? MyFaces 1.1.x and MyFaces 1.2.x have more the nature of two separate development trunks because they implement different specs. The Tomcat guys address such issues in the way I just described. So, why not learn from them? So, if we follow that path consistently our (sub)projects will each have the following structure: /branches /branches/1_1_6 /branches/1_2_1 /tags /tags/1_1_2 /tags/1_1_3 /tags/1_1_4 /tags/1_1_5 /tags/1_2_0 /tags/1_2_1 /1_1_x <--- the trunk for JSF 1.1 development /1_2_x <--- the trunk for JSF 1.2 development The great advantage: We can do this step by step without breaking anything. All we need to do is point the externals in the "current" project to the right trunk folder. We even can do the restructuring first and point the externals to the corresponding "1_1_x" trunks and in a second step switch "current" to the "1_2_x" trunks without a need to restructure again. WDYT? --Manfred On 4/18/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: > +1 but without a merge of the 1.1 trunk into 1.2. We have to select > each individual issue. That is quite time consuming and shouldn't be > done with this step. > > What about this: > move current trunk to a 1.1 branch and > move current 1.2 branch to trunk. > > That is quite a small step without any side effects to the existing code base. > > Cheers, > Mathias > > 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: > > Hi *, > > > > this is a formal vote on using the 1.2 branch as current now. > > > > Steps in doing this: > > > > - branch the current head as 1.1.5_1 > > - merge down the 1.2 branch to current head (that will be a lot of > > work, I'll tackle it) > > > > my +1 for doing this right now. > > > > regards, > > > > Martin > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Mathias
Re: Use 1.2 as current
+1 non-binding Gary -- Original message -- From: "Martin Marinschek" <[EMAIL PROTECTED]> > Hi *, > > this is a formal vote on using the 1.2 branch as current now. > > Steps in doing this: > > - branch the current head as 1.1.5_1 > - merge down the 1.2 branch to current head (that will be a lot of > work, I'll tackle it) > > my +1 for doing this right now. > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces
Re: Use 1.2 as current
Ok - first for merging: I'll try to do it, but will refrain from doing so if it gets too hard. We'll see if it works or if it doesn't. second for branches/tags/trunk renaming: I think that Manfred's suggestion has merits. We can go with this. regards, Martin On 4/18/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: +1 for making the 1.2 tag the "main show". I'm pretty confident that merging is no longer an option. The code bases have been separate for more than six months and they are very different. Plenty commits from several of us have touched 30 or 40 files at a time. Dennis Byrne On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Hi *, > > this is a formal vote on using the 1.2 branch as current now. > > Steps in doing this: > > - branch the current head as 1.1.5_1 > - merge down the 1.2 branch to current head (that will be a lot of > work, I'll tackle it) > > my +1 for doing this right now. > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- Dennis Byrne -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current
+1 for making the 1.2 tag the "main show". I'm pretty confident that merging is no longer an option. The code bases have been separate for more than six months and they are very different. Plenty commits from several of us have touched 30 or 40 files at a time. Dennis Byrne On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: Hi *, this is a formal vote on using the 1.2 branch as current now. Steps in doing this: - branch the current head as 1.1.5_1 - merge down the 1.2 branch to current head (that will be a lot of work, I'll tackle it) my +1 for doing this right now. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Dennis Byrne
Re: Use 1.2 as current
Yes. +1 for a switch But let's discuss the "how" first. Just had a look at the tomcat repo and I like the structure they use. Main issue is that they do not name their trunk folder "trunk" but rather give it a name corresponding to the actual major/minor version (eg "tc5.5.x"). I like this idea. And what is more: moving the current trunk to branches sounds weird to me. The 1.1.x is no branch and never will be a real branch of 1.2.x. So, why force it into the branches folder? MyFaces 1.1.x and MyFaces 1.2.x have more the nature of two separate development trunks because they implement different specs. The Tomcat guys address such issues in the way I just described. So, why not learn from them? So, if we follow that path consistently our (sub)projects will each have the following structure: /branches /branches/1_1_6 /branches/1_2_1 /tags /tags/1_1_2 /tags/1_1_3 /tags/1_1_4 /tags/1_1_5 /tags/1_2_0 /tags/1_2_1 /1_1_x <--- the trunk for JSF 1.1 development /1_2_x <--- the trunk for JSF 1.2 development The great advantage: We can do this step by step without breaking anything. All we need to do is point the externals in the "current" project to the right trunk folder. We even can do the restructuring first and point the externals to the corresponding "1_1_x" trunks and in a second step switch "current" to the "1_2_x" trunks without a need to restructure again. WDYT? --Manfred On 4/18/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: +1 but without a merge of the 1.1 trunk into 1.2. We have to select each individual issue. That is quite time consuming and shouldn't be done with this step. What about this: move current trunk to a 1.1 branch and move current 1.2 branch to trunk. That is quite a small step without any side effects to the existing code base. Cheers, Mathias 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: > Hi *, > > this is a formal vote on using the 1.2 branch as current now. > > Steps in doing this: > > - branch the current head as 1.1.5_1 > - merge down the 1.2 branch to current head (that will be a lot of > work, I'll tackle it) > > my +1 for doing this right now. > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current
+1 but without a merge of the 1.1 trunk into 1.2. We have to select each individual issue. That is quite time consuming and shouldn't be done with this step. What about this: move current trunk to a 1.1 branch and move current 1.2 branch to trunk. That is quite a small step without any side effects to the existing code base. Cheers, Mathias 2007/4/18, Martin Marinschek <[EMAIL PROTECTED]>: Hi *, this is a formal vote on using the 1.2 branch as current now. Steps in doing this: - branch the current head as 1.1.5_1 - merge down the 1.2 branch to current head (that will be a lot of work, I'll tackle it) my +1 for doing this right now. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current
:-) +1 On 4/18/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: On 18/04/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: > +1 > > This will help to "finish" the 1.2 development. I am not sure about a > complete merge of the head and the 1.2 branch (it is a lot of work!). > Maybe I will put the 1.2 branch as trunk and apply fixes (maybe Read "I would put" instead of "I will" :-) > existing fixes in for 1.1) in the trunk as the issues arise?) However, > if you want to tackle the merge, I am up for it... :-) > > Cheers > > Bruno > > On 18/04/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > Hi *, > > > > this is a formal vote on using the 1.2 branch as current now. > > > > Steps in doing this: > > > > - branch the current head as 1.1.5_1 > > - merge down the 1.2 branch to current head (that will be a lot of > > work, I'll tackle it) > > > > my +1 for doing this right now. > > > > regards, > > > > Martin > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Use 1.2 as current
On 18/04/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: +1 This will help to "finish" the 1.2 development. I am not sure about a complete merge of the head and the 1.2 branch (it is a lot of work!). Maybe I will put the 1.2 branch as trunk and apply fixes (maybe Read "I would put" instead of "I will" :-) existing fixes in for 1.1) in the trunk as the issues arise?) However, if you want to tackle the merge, I am up for it... :-) Cheers Bruno On 18/04/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Hi *, > > this is a formal vote on using the 1.2 branch as current now. > > Steps in doing this: > > - branch the current head as 1.1.5_1 > - merge down the 1.2 branch to current head (that will be a lot of > work, I'll tackle it) > > my +1 for doing this right now. > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
Re: Use 1.2 as current
+1 This will help to "finish" the 1.2 development. I am not sure about a complete merge of the head and the 1.2 branch (it is a lot of work!). Maybe I will put the 1.2 branch as trunk and apply fixes (maybe existing fixes in for 1.1) in the trunk as the issues arise?) However, if you want to tackle the merge, I am up for it... :-) Cheers Bruno On 18/04/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: Hi *, this is a formal vote on using the 1.2 branch as current now. Steps in doing this: - branch the current head as 1.1.5_1 - merge down the 1.2 branch to current head (that will be a lot of work, I'll tackle it) my +1 for doing this right now. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current
What is in head that needs to be merged with the 1.2 branch? Why not move head to 1.1.5_1 and move 1.2 to head? I'm rather worried that the spec compliance will go down drastically if there are extensive merges. thanks david jencks On Apr 18, 2007, at 1:35 AM, Martin Marinschek wrote: Hi *, this is a formal vote on using the 1.2 branch as current now. Steps in doing this: - branch the current head as 1.1.5_1 - merge down the 1.2 branch to current head (that will be a lot of work, I'll tackle it) my +1 for doing this right now. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Use 1.2 as current now
Erik, JSF 1.2 also requires 1.5 the MYFACES_1_1_X branch will stay w/ Java 1.4 (or 1.3; not sure what the spec wants). -M On 4/18/07, Scheper, Erik-Berndt <[EMAIL PROTECTED]> wrote: Sounds like a good idea. One question however: Tomcat 6 requires JDK 5. Does this mean that the trunk will drop JDK 1.4 compatibility? Regards, Erik-Berndt -Oorspronkelijk bericht- Van: Martin Marinschek [mailto:[EMAIL PROTECTED] Verzonden: woensdag 18 april 2007 10:07 Aan: MyFaces Development Onderwerp: Use 1.2 as current now Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Use 1.2 as current now
Ok, I'll start a vote - this is important enough that we should do a vote. regards, Martin On 4/18/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Jetty is also ready ;) On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Hi *, > > I wonder if we should switch the trunk to be the 1.2 branch now, cause > our next release will surely be fully 1.2 compatible (Tomcat 6 is out > now, so the sooner we're done, the better)... We'll have a lot better > testing of 1.2 if we do it like this - wdyt? > > regards, > > Martin > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: 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
Re: Use 1.2 as current now
Jetty is also ready ;) On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
RE: Use 1.2 as current now
Sounds like a good idea. One question however: Tomcat 6 requires JDK 5. Does this mean that the trunk will drop JDK 1.4 compatibility? Regards, Erik-Berndt -Oorspronkelijk bericht- Van: Martin Marinschek [mailto:[EMAIL PROTECTED] Verzonden: woensdag 18 april 2007 10:07 Aan: MyFaces Development Onderwerp: Use 1.2 as current now Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Use 1.2 as current now
+1 On 4/18/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: Hi *, I wonder if we should switch the trunk to be the 1.2 branch now, cause our next release will surely be fully 1.2 compatible (Tomcat 6 is out now, so the sooner we're done, the better)... We'll have a lot better testing of 1.2 if we do it like this - wdyt? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com