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
+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
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
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
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
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
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
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
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
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
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
