Re: [VOTE] release for myfaces core 2.0.0-beta
Not entirely true, there are two types of events that need to be processed. ApplicationImpl handles only one of them (the component system events). These are registered on a component. The patch provides support for the other type: global system events. These are registered by invoking Appliaction.subscribeToEvent. But I don't think it's important enough to delay the release. Regards, Jan-Kees 2010/1/26 Leonardo Uribe lu4...@gmail.com: Hi About @ListenerFor: It is working as expected. I don't think the patch provided will work, because this annotation is handled on ApplicationImpl (because the annotations must be read when the component/renderer is created). About MYFACES-2356 (decode behavior for UISelectOne components): I did another patch that implements the change proposed on the renderkitdoc. Michael, could you try if this patch works as expected? If so, I'll restart the vote. regards, Leonardo Uribe 2010/1/25 Jan-Kees van Andel jankeesvanan...@gmail.com Hi Leonardo, Are you gonna rebuild now? I just submitted a patch with support for the @ListenerFor/@ListenersFor annotations to handle global system events. See MYFACES-2509 I'm quite sure it doesn't break anything, but I don't want to introduce any risks short before the beta release so if someone can review the patch we might be able to include it... Regards, Jan-Kees 2010/1/25 Leonardo Uribe lu4...@gmail.com: Ok, I'll commit that patch on the branch, rebuild all artifacts and ask for a vote again. Thanks for the information. 2010/1/25 Michael Kurz michi.k...@gmx.at -1 I have to revise my vote because I found a bug that should not be in the beta version. See patch and comment on MYFACES-2356 for details. rgards Michael Am 22.01.2010 10:49, schrieb Jakob Korherr: +1 Regards, Jakob 2010/1/22 Michael Kurz michi.k...@gmx.at mailto:michi.k...@gmx.at +1 Am 22.01.2010 08:55, schrieb Gerhard Petracek: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/22 Werner Punz werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com +1 Matthias Wessendorf schrieb: +1 On Fri, Jan 22, 2010 at 7:03 AM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. The artifacts passed all TCK test that in my personal opinion should pass, but we can't claim it oficially, because we are waiting a response from Sun. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta http://people.apache.org/%7Elu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc http://people.apache.org/%7Elu4242/myfaces200betabinsrc [4] http://issues.apache.org/jira/browse/MYFACES (jira is
[jira] Commented: (MYFACES-2509) @ListenerFor not processed for global system events
[ https://issues.apache.org/jira/browse/MYFACES-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804952#action_12804952 ] Jan-Kees van Andel commented on MYFACES-2509: - Hrm, it looks like the JavaDoc can be interpreted in multiple ways. What I read, is that it should be possible for classes that implement SystemEventListener, to listen to SystemEvents. For example: http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/javax/faces/event/PostConstructApplicationEvent.html The current implementation cannot deal with this event, because it occurs before the ApplicationImpl code is invoked (there is no component tree at that time). For this reason, we need to check it @startup. But because its so ambiguous, I suggest to leave it out of the beta release. @ListenerFor not processed for global system events --- Key: MYFACES-2509 URL: https://issues.apache.org/jira/browse/MYFACES-2509 Project: MyFaces Core Issue Type: New Feature Components: JSR-314 Affects Versions: 2.0.0-alpha Reporter: Jan-Kees van Andel Assignee: Jan-Kees van Andel Attachments: ListenerFor_support.patch We currently don't process @ListenerFor and @ListenerFor annotations on non-component types. This is specified in the spec for global system events, see: http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/index.html?javax/faces/event/ListenerFor.html It would be nice to have it in the beta. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] release for myfaces core 2.0.0-beta
Hi Leonardo, Your response triggered me to read the JavaDocs again from your point of view. It looks like the spec is not very clear on this. I've commented on the issue in JIRA, as follows: Hrm, it looks like the JavaDoc can be interpreted in multiple ways. What I read, is that it should be possible for classes that implement SystemEventListener, to listen to SystemEvents. For example: http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/javax/faces/event/PostConstructApplicationEvent.html The current implementation cannot deal with this event, because it occurs before the ApplicationImpl code is invoked (there is no component tree at that time). For this reason, we need to check it @startup. But because its so ambiguous, I suggest to leave it out of the beta release. I would say, let's keep it out of this release... :-) Regards, Jan-Kees 2010/1/26 Jan-Kees van Andel jankeesvanan...@gmail.com: Not entirely true, there are two types of events that need to be processed. ApplicationImpl handles only one of them (the component system events). These are registered on a component. The patch provides support for the other type: global system events. These are registered by invoking Appliaction.subscribeToEvent. But I don't think it's important enough to delay the release. Regards, Jan-Kees 2010/1/26 Leonardo Uribe lu4...@gmail.com: Hi About @ListenerFor: It is working as expected. I don't think the patch provided will work, because this annotation is handled on ApplicationImpl (because the annotations must be read when the component/renderer is created). About MYFACES-2356 (decode behavior for UISelectOne components): I did another patch that implements the change proposed on the renderkitdoc. Michael, could you try if this patch works as expected? If so, I'll restart the vote. regards, Leonardo Uribe 2010/1/25 Jan-Kees van Andel jankeesvanan...@gmail.com Hi Leonardo, Are you gonna rebuild now? I just submitted a patch with support for the @ListenerFor/@ListenersFor annotations to handle global system events. See MYFACES-2509 I'm quite sure it doesn't break anything, but I don't want to introduce any risks short before the beta release so if someone can review the patch we might be able to include it... Regards, Jan-Kees 2010/1/25 Leonardo Uribe lu4...@gmail.com: Ok, I'll commit that patch on the branch, rebuild all artifacts and ask for a vote again. Thanks for the information. 2010/1/25 Michael Kurz michi.k...@gmx.at -1 I have to revise my vote because I found a bug that should not be in the beta version. See patch and comment on MYFACES-2356 for details. rgards Michael Am 22.01.2010 10:49, schrieb Jakob Korherr: +1 Regards, Jakob 2010/1/22 Michael Kurz michi.k...@gmx.at mailto:michi.k...@gmx.at +1 Am 22.01.2010 08:55, schrieb Gerhard Petracek: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/22 Werner Punz werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com +1 Matthias Wessendorf schrieb: +1 On Fri, Jan 22, 2010 at 7:03 AM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. The artifacts passed all TCK test that in my personal opinion should pass, but we can't claim it oficially, because we are waiting a response from Sun. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of
[jira] Commented: (MYFACES-2356) HtmlRadioRendererBase calls converter method getAsString() not with the object, but with the string version when an validation error occured
[ https://issues.apache.org/jira/browse/MYFACES-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804956#action_12804956 ] Jakob Korherr commented on MYFACES-2356: I'm sorry that I don't have time to test this right now (I'm a little busy with university stuff), but please also check the behavior of UISelectMany components before the release, because they also use most of this code! HtmlRadioRendererBase calls converter method getAsString() not with the object, but with the string version when an validation error occured Key: MYFACES-2356 URL: https://issues.apache.org/jira/browse/MYFACES-2356 Project: MyFaces Core Issue Type: Bug Components: General Reporter: Jakob Korherr Assignee: Jakob Korherr Priority: Minor Fix For: 2.0.0-beta Attachments: HtmlRadioRendererBase.patch, MYFACES-2356-2.patch, MYFACES-2356-3.patch If you have a h:selectOneRadio component with some SelectItems and you select an item, submit it and an validation error occurs, HtmlRadioRendererBase calls org.apache.myfaces.shared_impl.renderkit.RendererUtils.getConvertedStringValue() with the submitted value, which is not converted an therefore already the string version of the SelectItem. So the provided converter tries to convert the string version to the string version, which can end in strange behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[OFFTOPIC] JSFDays 2010 Vienna
Hi all, we'd like to invite you to come to a JSF conference in Vienna, Austria from 23rd-25th of February. The program is packed with the latest and greatest information about JSF 2.0 and the new versions of the major component libraries as well as extensions. It will be worthwhile for you as a JSF developer to hear what this new version of JSF has to offer. In addition to the JSF track, there will also be a general Java EE track where the important new developments in the Java EE space will be covered. Additionally, the third day hosts a series of workshops on such interesting topics as: - Collaboration with Ajax Push, ICEfaces 2, and JSF 2 - RichFaces 4 with JSF 2 - The Java Memory Model - Real World Java EE (Patterns) - Rethinking Best Practices - Developing loosely coupled services - Hands on with the Portlet Bridge - Go Fullstack: JSF, Spring, JPA perfectly linked Here is the link: http://conference.irian.at - click on “Registration”. Attendees will pay a very small conference fee - 360,- Euro (including 20% VAT). The third day - the workshop day - will be charged separately. The attendance fee for the workshop day is 600,- Euro (including 20% VAT) per person. There will be a supporting program alongside the conference - so you will (additionally to learning about JSF and improving your JSF knowledge) have a good chance of getting to know Vienna and its surroundings. So far, there have been a lot registrations - so this conference is definitely going to be a meeting point for everyone interested in JSF! Regards, Gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [VOTE] release for myfaces core 2.0.0-beta
Works as expected. - Michael Am 26.01.2010 06:55, schrieb Leonardo Uribe: Hi About @ListenerFor: It is working as expected. I don't think the patch provided will work, because this annotation is handled on ApplicationImpl (because the annotations must be read when the component/renderer is created). About MYFACES-2356 (decode behavior for UISelectOne components): I did another patch that implements the change proposed on the renderkitdoc. Michael, could you try if this patch works as expected? If so, I'll restart the vote. regards, Leonardo Uribe 2010/1/25 Jan-Kees van Andel jankeesvanan...@gmail.com mailto:jankeesvanan...@gmail.com Hi Leonardo, Are you gonna rebuild now? I just submitted a patch with support for the @ListenerFor/@ListenersFor annotations to handle global system events. See MYFACES-2509 I'm quite sure it doesn't break anything, but I don't want to introduce any risks short before the beta release so if someone can review the patch we might be able to include it... Regards, Jan-Kees 2010/1/25 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com: Ok, I'll commit that patch on the branch, rebuild all artifacts and ask for a vote again. Thanks for the information. 2010/1/25 Michael Kurz michi.k...@gmx.at mailto:michi.k...@gmx.at -1 I have to revise my vote because I found a bug that should not be in the beta version. See patch and comment on MYFACES-2356 for details. rgards Michael Am 22.01.2010 10:49, schrieb Jakob Korherr: +1 Regards, Jakob 2010/1/22 Michael Kurz michi.k...@gmx.at mailto:michi.k...@gmx.at mailto:michi.k...@gmx.at mailto:michi.k...@gmx.at +1 Am 22.01.2010 08:55, schrieb Gerhard Petracek: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/22 Werner Punz werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com mailto:werner.p...@gmail.com +1 Matthias Wessendorf schrieb: +1 On Fri, Jan 22, 2010 at 7:03 AM, Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com mailto:lu4...@gmail.com wrote: Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. The artifacts passed all TCK test that in my personal opinion should pass, but we can't claim it oficially, because we are waiting a response from Sun. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe
[jira] Commented: (MYFACES-2356) HtmlRadioRendererBase calls converter method getAsString() not with the object, but with the string version when an validation error occured
[ https://issues.apache.org/jira/browse/MYFACES-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804969#action_12804969 ] Michael Kurz commented on MYFACES-2356: --- Hi Leonardo, patch MYFACES-2356-3 works for me without problems. We could probably completely remove RendererUtils.NOTHING but preferably not before the beta release as this should not have any impact. I will create another issue and a patch. HtmlRadioRendererBase calls converter method getAsString() not with the object, but with the string version when an validation error occured Key: MYFACES-2356 URL: https://issues.apache.org/jira/browse/MYFACES-2356 Project: MyFaces Core Issue Type: Bug Components: General Reporter: Jakob Korherr Assignee: Jakob Korherr Priority: Minor Fix For: 2.0.0-beta Attachments: HtmlRadioRendererBase.patch, MYFACES-2356-2.patch, MYFACES-2356-3.patch If you have a h:selectOneRadio component with some SelectItems and you select an item, submit it and an validation error occurs, HtmlRadioRendererBase calls org.apache.myfaces.shared_impl.renderkit.RendererUtils.getConvertedStringValue() with the submitted value, which is not converted an therefore already the string version of the SelectItem. So the provided converter tries to convert the string version to the string version, which can end in strange behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Calendar problem in Opera
Hello. I found a little bug in Tomahawk calendar in Opera. When I open the calendar, it shows the current year as 3910. I fixed this problem, may I send my code to this list?
Re: Calendar problem in Opera
hello, it's nice to hear that you already have a patch. please create an issue at [1] and attach your patch. regards, gerhard [1] https://issues.apache.org/jira/browse/TOMAHAWK http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/26 Guilherme Garnier guilherme.garn...@gmail.com Hello. I found a little bug in Tomahawk calendar in Opera. When I open the calendar, it shows the current year as 3910. I fixed this problem, may I send my code to this list?
[vote] MyFaces Master pom v7
This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [vote] MyFaces Master pom v7
+1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (TOMAHAWK-1480) Calendar shows wrong year in Opera
Calendar shows wrong year in Opera -- Key: TOMAHAWK-1480 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1480 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Environment: Opera 10.10 Reporter: Guilherme Garnier Priority: Minor When using Opera, the calendar opens in the wrong year (current year + 1900), although it´s correctly displayed in the calendar footer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Calendar problem in Opera
Done: https://issues.apache.org/jira/browse/TOMAHAWK-1480 On Tue, Jan 26, 2010 at 9:36 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hello, it's nice to hear that you already have a patch. please create an issue at [1] and attach your patch. regards, gerhard [1] https://issues.apache.org/jira/browse/TOMAHAWK http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/26 Guilherme Garnier guilherme.garn...@gmail.com Hello. I found a little bug in Tomahawk calendar in Opera. When I open the calendar, it shows the current year as 3910. I fixed this problem, may I send my code to this list?
Re: [vote] MyFaces Master pom v7
+1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (TRINIDAD-1697) New Trinidad Components Showcase demo application
New Trinidad Components Showcase demo application - Key: TRINIDAD-1697 URL: https://issues.apache.org/jira/browse/TRINIDAD-1697 Project: MyFaces Trinidad Issue Type: New Feature Reporter: Cosmin Martinconi A new and improved Trinidad components showcase demo application: - the demo is working only with facelets (there is no jsp version) - we tried to build it so it can be searched online also, currently tried with Google Custom Search, but this didn't work out so smoothly so far. - in general, it replicates the examples available already for Trinidad in the existing demo, in some places slightly or more improved. - it tries to provide a platform on which to build much more demos as required as there can be always new ideas about demoing a meaningfull use case on Trinidad, or some component behavior. I have attached the zip file, containing the source code of the showcase Regards, Cosmin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1698) JavaScript page malfunction on chooseDate month/year dropdown change
JavaScript page malfunction on chooseDate month/year dropdown change
Key: TRINIDAD-1698
URL: https://issues.apache.org/jira/browse/TRINIDAD-1698
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.0.10-core
Environment: Windows XP, Internet Explorer 7
Reporter: Nathan Hansford
When using a tr:inputDate in conjunction with a tr:chooseDate such as the
following:
tr:inputDate id=datePick value=#{TestBean.date} chooseId=dateChooser
f:convertDateTime dateStyle=long /
/tr:inputDate
tr:chooseDate id=dateChooser /
the page begins to malfunction after changing the month or year via the
drop-down boxes in the tr:chooseDate. Afterward, when a different control is
used such as the following:
tr:outputLabel value=Products /
tr:selectOneChoice value=#{TestBean.product} id=productSelect
autoSubmit=true valueChangeListener=#TestBean.productChange}
f:selectItems value=#{TestBean.products} /
/tr:selectOneChoice
tr:outputLabel value=Policy Type /
tr:selectOneChoice value= id=policyTypeSelect autoSubmit=false
partialTriggers=productSelect
f:selectItems value=#{TestBean.policyTypes} /
/tr:selectOneChoice
The components do not function properly, resulting in a JavaScript alert pop-up
box showing and containing no message. Upon submitting the form, an HTTP
Status 400 occurs with the following message The request sent by the client
was syntactically incorrect ().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1697) New Trinidad Components Showcase demo application
[ https://issues.apache.org/jira/browse/TRINIDAD-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805064#action_12805064 ] Matthias Weßendorf commented on TRINIDAD-1697: -- hi cool stuff this should go under trinidad-examples: http://svn.apache.org/repos/asf/myfaces/trinidad/trunk/trinidad-examples/ as an additional demo. Though, we should make this our default demo :-) -Matthias New Trinidad Components Showcase demo application - Key: TRINIDAD-1697 URL: https://issues.apache.org/jira/browse/TRINIDAD-1697 Project: MyFaces Trinidad Issue Type: New Feature Reporter: Cosmin Martinconi Attachments: trinidad-components-showcase.zip A new and improved Trinidad components showcase demo application: - the demo is working only with facelets (there is no jsp version) - we tried to build it so it can be searched online also, currently tried with Google Custom Search, but this didn't work out so smoothly so far. - in general, it replicates the examples available already for Trinidad in the existing demo, in some places slightly or more improved. - it tries to provide a platform on which to build much more demos as required as there can be always new ideas about demoing a meaningfull use case on Trinidad, or some component behavior. I have attached the zip file, containing the source code of the showcase Regards, Cosmin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [vote] MyFaces Master pom v7
No opinion on voting, I am just curious why the master is being released, what changed? -Andrew On Tue, Jan 26, 2010 at 7:10 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [vote] MyFaces Master pom v7
we added a bunch of new committers; updated to Apache POM v7 -Matthias On Tue, Jan 26, 2010 at 5:38 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: No opinion on voting, I am just curious why the master is being released, what changed? -Andrew On Tue, Jan 26, 2010 at 7:10 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [vote] MyFaces Master pom v7
+1 2010/1/26 Matthias Wessendorf mat...@apache.org: we added a bunch of new committers; updated to Apache POM v7 -Matthias On Tue, Jan 26, 2010 at 5:38 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: No opinion on voting, I am just curious why the master is being released, what changed? -Andrew On Tue, Jan 26, 2010 at 7:10 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (MYFACES-2510) Remove RendererUtils.NOTHING
Remove RendererUtils.NOTHING Key: MYFACES-2510 URL: https://issues.apache.org/jira/browse/MYFACES-2510 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Affects Versions: 2.0.0-beta-2 Reporter: Michael Kurz Attachments: MYFACES-2510.patch According to the spec, the submitted value for UISelectOne components must be set to the empty string if there is no entry in the request parameter map. Though this change is already covered in MYFACES-2356, some cleanup work remains to be done. Previously the submitted value was set to RendererUtils.NOTHING in this case. As this is no longer needed, it should be removed completely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-2510) Remove RendererUtils.NOTHING
[ https://issues.apache.org/jira/browse/MYFACES-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Kurz updated MYFACES-2510: -- Status: Patch Available (was: Open) Remove RendererUtils.NOTHING Key: MYFACES-2510 URL: https://issues.apache.org/jira/browse/MYFACES-2510 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Affects Versions: 2.0.0-beta-2 Reporter: Michael Kurz Attachments: MYFACES-2510.patch According to the spec, the submitted value for UISelectOne components must be set to the empty string if there is no entry in the request parameter map. Though this change is already covered in MYFACES-2356, some cleanup work remains to be done. Previously the submitted value was set to RendererUtils.NOTHING in this case. As this is no longer needed, it should be removed completely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1699) Provide isSecure on ExternalContextUtils
Provide isSecure on ExternalContextUtils Key: TRINIDAD-1699 URL: https://issues.apache.org/jira/browse/TRINIDAD-1699 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 1.2.12-core Reporter: Andrew Robinson Assignee: Andrew Robinson Due to some unknown reason, the JSF RI did not provide an public boolean isSecure(); on ExternalContext even though both ServletRequest and PortletRequest have that method. As such, it will be helpful to have it provided as API on ExternalContextUtils -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1699) Provide isSecure on ExternalContextUtils
[ https://issues.apache.org/jira/browse/TRINIDAD-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805103#action_12805103 ] Matthias Weßendorf commented on TRINIDAD-1699: -- that's an item for the spec. Do you mind filing a bug against the JSF 2.x spec ? Provide isSecure on ExternalContextUtils Key: TRINIDAD-1699 URL: https://issues.apache.org/jira/browse/TRINIDAD-1699 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 1.2.12-core Reporter: Andrew Robinson Assignee: Andrew Robinson Due to some unknown reason, the JSF RI did not provide an public boolean isSecure(); on ExternalContext even though both ServletRequest and PortletRequest have that method. As such, it will be helpful to have it provided as API on ExternalContextUtils -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1700) Cache renderer type from getRenderer in UIXComponentBase
Cache renderer type from getRenderer in UIXComponentBase Key: TRINIDAD-1700 URL: https://issues.apache.org/jira/browse/TRINIDAD-1700 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.12-core Reporter: Stevan Malesevic UIXComponentBase has a cached renderer. Howevere, renderer is put in cache during encodeBegin or __rendererDecode which is quite late. Number of calls to getClientId will happen before and will need to get renderer whcih is expensive. We should cache renerer when getrenderer is invoked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1689) New Trinidad Default Skin - Casablanca
[ https://issues.apache.org/jira/browse/TRINIDAD-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Catalin Kormos updated TRINIDAD-1689: - Resolution: Fixed Status: Resolved (was: Patch Available) Patch applied. New Trinidad Default Skin - Casablanca -- Key: TRINIDAD-1689 URL: https://issues.apache.org/jira/browse/TRINIDAD-1689 Project: MyFaces Trinidad Issue Type: New Feature Components: Skinning Affects Versions: 1.2.14-core Reporter: Adonis Raul Raduca Assignee: Catalin Kormos Fix For: 1.2.14-core Attachments: casablanca.zip, casablancaIntegration.patch, trinidadAdaptation.patch A new more modern skin with a nice-minimalist look. Also a simple and intuitive way to skin Trinidad components using Casablanca selectors stack. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1699) Provide isSecure on ExternalContextUtils
[ https://issues.apache.org/jira/browse/TRINIDAD-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Robinson resolved TRINIDAD-1699. --- Resolution: Fixed Provide isSecure on ExternalContextUtils Key: TRINIDAD-1699 URL: https://issues.apache.org/jira/browse/TRINIDAD-1699 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 1.2.13-core Reporter: Andrew Robinson Assignee: Andrew Robinson Due to some unknown reason, the JSF RI did not provide an public boolean isSecure(); on ExternalContext even though both ServletRequest and PortletRequest have that method. As such, it will be helpful to have it provided as API on ExternalContextUtils -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-53) Static imports in bytecode dependency scanner ignored
[ https://issues.apache.org/jira/browse/EXTSCRIPT-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-53. -- Resolution: Fixed Static imports in bytecode dependency scanner ignored - Key: EXTSCRIPT-53 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-53 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee: Werner Punz Priority: Minor static imports for now are ignored in our bytecode dependency scanner -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-49) Renderers stay tainted after refresh
[ https://issues.apache.org/jira/browse/EXTSCRIPT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-49. -- Resolution: Fixed Renderers stay tainted after refresh Key: EXTSCRIPT-49 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-49 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee: Werner Punz Priority: Minor Investigate and fix why renderers stay tainted after a refresh -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1699) Provide isSecure on ExternalContextUtils
[ https://issues.apache.org/jira/browse/TRINIDAD-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805146#action_12805146 ] Andrew Robinson commented on TRINIDAD-1699: --- Filed a mojarra bug: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1524 Provide isSecure on ExternalContextUtils Key: TRINIDAD-1699 URL: https://issues.apache.org/jira/browse/TRINIDAD-1699 Project: MyFaces Trinidad Issue Type: Improvement Affects Versions: 1.2.13-core Reporter: Andrew Robinson Assignee: Andrew Robinson Fix For: 1.2.14-core Due to some unknown reason, the JSF RI did not provide an public boolean isSecure(); on ExternalContext even though both ServletRequest and PortletRequest have that method. As such, it will be helpful to have it provided as API on ExternalContextUtils -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RESULT - Re: [Vote] Trinidad 1.2.13 release
Hello, thanks for voting. We got 6 votes, all were +1: -Matt Cooper -Gerhard Petracek -Cagatay Civici -Max Starets -Jan-Kees van Andel -Matthias Wessendorf I will follow up with the required steps to get the release out. -Matthias On Mon, Jan 25, 2010 at 8:34 PM, Matt Cooper mcoo...@apache.org wrote: +1 On Mon, Jan 25, 2010 at 11:36 AM, Max Starets max.star...@oracle.com wrote: +1 Matthias Wessendorf wrote: Hi, I was running the needed tasks to get the 1.2.13 release of the Apache MyFaces Trinidad CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.13 artifacts and vote [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/core_1_2_13/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [vote] MyFaces Master pom v7
+1 Regards, Jakob 2010/1/26 Bruno Aranda brunoara...@gmail.com +1 2010/1/26 Matthias Wessendorf mat...@apache.org: we added a bunch of new committers; updated to Apache POM v7 -Matthias On Tue, Jan 26, 2010 at 5:38 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: No opinion on voting, I am just curious why the master is being released, what changed? -Andrew On Tue, Jan 26, 2010 at 7:10 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [vote] MyFaces Master pom v7
+1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/26 Bruno Aranda brunoara...@gmail.com +1 2010/1/26 Matthias Wessendorf mat...@apache.org: we added a bunch of new committers; updated to Apache POM v7 -Matthias On Tue, Jan 26, 2010 at 5:38 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: No opinion on voting, I am just curious why the master is being released, what changed? -Andrew On Tue, Jan 26, 2010 at 7:10 AM, Jan-Kees van Andel jankeesvanan...@gmail.com wrote: +1 2010/1/26 Matthias Wessendorf mat...@apache.org: +1 On Tue, Jan 26, 2010 at 12:46 PM, Matthias Wessendorf mat...@apache.org wrote: This is the formal vote for the new myfaces master POM version 7. You can find the signed release candidate at [1]. Please vote +1 if you reviewed the new master pom version 7 and think we can use it -1 if you found a flaw or potential problem with the new master pom Thanks, Matthias [1] http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/myfaces/7 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (EXTSCRIPT-54) Add also annotation handling in the bytecode dependency scanner
Add also annotation handling in the bytecode dependency scanner --- Key: EXTSCRIPT-54 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-54 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2511) Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly
Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly - Key: MYFACES-2511 URL: https://issues.apache.org/jira/browse/MYFACES-2511 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr If javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR is set to true, the BeanValidator is not installed automatically on all input components. This already works fine. However, the BeanValidator can still be added manually via f:validateBean /, which is not handled correctly at the moment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2512) Ensure invocation of nextHandler.apply() in ValidatorTagHandlerDelegate when in wrapping-mode
Ensure invocation of nextHandler.apply() in ValidatorTagHandlerDelegate when in wrapping-mode - Key: MYFACES-2512 URL: https://issues.apache.org/jira/browse/MYFACES-2512 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr Currently nextHandler.apply() is not invoked if the validator is disabled and it has no (or just an empty) validatorId or if the validator is enabled and it has no or empty validationGroups. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] release for myfaces core 2.0.0-beta
Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537
[jira] Resolved: (MYFACES-2512) Ensure invocation of nextHandler.apply() in ValidatorTagHandlerDelegate when in wrapping-mode
[ https://issues.apache.org/jira/browse/MYFACES-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2512. Resolution: Fixed Fix Version/s: 2.0.0-beta-2 Ensure invocation of nextHandler.apply() in ValidatorTagHandlerDelegate when in wrapping-mode - Key: MYFACES-2512 URL: https://issues.apache.org/jira/browse/MYFACES-2512 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Jakob Korherr Assignee: Jakob Korherr Fix For: 2.0.0-beta-2 Currently nextHandler.apply() is not invoked if the validator is disabled and it has no (or just an empty) validatorId or if the validator is enabled and it has no or empty validationGroups. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] release for myfaces core 2.0.0-beta
+1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200betahttp://people.apache.org/%7Elu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrchttp://people.apache.org/%7Elu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537
Re: [VOTE] release for myfaces core 2.0.0-beta
+1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200betahttp://people.apache.org/%7Elu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrchttp://people.apache.org/%7Elu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537
Re: [VOTE] release for myfaces core 2.0.0-beta
+1 2010/1/27 Leonardo Uribe lu4...@gmail.com: +1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537
[Announce] Release of Apache MyFaces Trinidad 1.2.13
The Apache MyFaces Trinidad team is pleased to announce the release of Apache MyFaces Trinidad Core 1.2.13. Apache MyFaces Trinidad is a JavaServer(tm) Faces 1.2 component library. Trinidad Core 1.2.13 is available in both binary and source distributions: * http://myfaces.apache.org/trinidad/download.html Apache MyFaces Trinidad is available in the central Maven repository under Group ID org.apache.myfaces.trinidad. Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661styleName=Htmlversion=12314170 Enjoy! Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] release for myfaces core 2.0.0-beta
+1 -Matthias On Wed, Jan 27, 2010 at 2:57 AM, Bruno Aranda brunoara...@gmail.com wrote: +1 2010/1/27 Leonardo Uribe lu4...@gmail.com: +1 2010/1/26 Jakob Korherr jakob.korh...@gmail.com +1 Regards, Jakob 2010/1/27 Leonardo Uribe lu4...@gmail.com Hi, I was running the needed tasks to get the 2.0.0-beta release of Apache MyFaces core out. This artifacts are very close to pass all TCK tests. Some corrections has been done from the latest proposed artifacts. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.shared v4.0.1-beta [1] 2. Maven artifact group org.apache.myfaces.core v2.0.0-beta [1] The artifacts are deployed to my private Apache account ([1] and [3] for binary and source packages). The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.0-beta artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://people.apache.org/~lu4242/myfaces200beta [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces200betabinsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12314537 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
