Re: [VOTE] Release Tobago 3.0.6
Here is my +1 Regards Bernd On Sat, Sep 16, 2017 at 8:12 AM, Dennis Kieselhorstwrote: > +1 > > Looks fine for me but please note that integration tests are failing in > 3.0.x branch and also in master: > https://builds.apache.org/view/M-R/view/MyFaces/job/ > Tobago%20Trunk%20integration-test/ >
[jira] [Commented] (TOBAGO-1794) Deploy different versions of Tobago demo in the VM
[ https://issues.apache.org/jira/browse/TOBAGO-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170576#comment-16170576 ] Hudson commented on TOBAGO-1794: SUCCESS: Integrated in Jenkins build Tobago Trunk #1028 (See [https://builds.apache.org/job/Tobago%20Trunk/1028/]) TOBAGO-1794: Deploy different versions of Tobago demo in the VM * minor (lofwyr: rev ae37287cd543b273fd7a8a518413cb922404ffb7) * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/apache-proxy/index.html > Deploy different versions of Tobago demo in the VM > --- > > Key: TOBAGO-1794 > URL: https://issues.apache.org/jira/browse/TOBAGO-1794 > Project: MyFaces Tobago > Issue Type: Task >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > > We have an VM to run the demo application on it (see INFRA-13538). > There should be run every newest version of each main branch and SNAPSHOTs of > the current development branches. Currently we have > * 1.0.42 (8010) > * 1.5.13 (8015) > * 2.1.0 (8020) > * 2.1.1-SNAPSHOT (8029) > * 3.0.5 (8030) > * 3.0.6-SNAPSHOT (8039) > * 4.0.0-SNAPSHOT (8049) > The runtime environment might be Docker. The portmapping may be done with > this rules: > 8xxy (where xx is the mayor version (except 1.5) and y = 0 for a release and > y = 9 for a SNAPSHOT'). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1794) Deploy different versions of Tobago demo in the VM
[ https://issues.apache.org/jira/browse/TOBAGO-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170543#comment-16170543 ] Hudson commented on TOBAGO-1794: SUCCESS: Integrated in Jenkins build Tobago Trunk #1027 (See [https://builds.apache.org/job/Tobago%20Trunk/1027/]) TOBAGO-1794: Deploy different versions of Tobago demo in the VM * (lofwyr: rev 7614353fdbdc0c43162ec0887ab1fd72dbaf67cd) * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/apache-proxy/Dockerfile * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/apache-proxy/000-default.conf * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/tomcat/deploy-and-run.sh * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/readme.md * (edit) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/docker-compose.yml * (add) tobago-example/tobago-example-demo/src/main/tobago-vm/docker/apache-proxy/index.html > Deploy different versions of Tobago demo in the VM > --- > > Key: TOBAGO-1794 > URL: https://issues.apache.org/jira/browse/TOBAGO-1794 > Project: MyFaces Tobago > Issue Type: Task >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > > We have an VM to run the demo application on it (see INFRA-13538). > There should be run every newest version of each main branch and SNAPSHOTs of > the current development branches. Currently we have > * 1.0.42 (8010) > * 1.5.13 (8015) > * 2.1.0 (8020) > * 2.1.1-SNAPSHOT (8029) > * 3.0.5 (8030) > * 3.0.6-SNAPSHOT (8039) > * 4.0.0-SNAPSHOT (8049) > The runtime environment might be Docker. The portmapping may be done with > this rules: > 8xxy (where xx is the mayor version (except 1.5) and y = 0 for a release and > y = 9 for a SNAPSHOT'). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group
[ https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170015#comment-16170015 ] Dora Rajappan edited comment on MYFACES-4153 at 9/18/17 2:03 PM: - I will provide the application. Its huge with ejbs etc.. So I have to find out how i can give that to you. I am new to rendering to quickly tweak a solution.:) was (Author: dorarajappan): I will provide the application. Its huge with ejbs etc.. So I have to find out how i can give that to you. I am new to rendering to quickly tweak a solution. > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group > --- > > Key: MYFACES-4153 > URL: https://issues.apache.org/jira/browse/MYFACES-4153 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.3.0-beta >Reporter: Dora Rajappan >Priority: Minor > > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group towards the left since it gets rendered as html > table. This is same behaviour for mojarra 2.2 also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group
[ https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170015#comment-16170015 ] Dora Rajappan commented on MYFACES-4153: I will provide the application. Its huge with ejbs etc.. So I have to find out how i can give that to you. I am new to rendering to quickly tweak a solution. > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group > --- > > Key: MYFACES-4153 > URL: https://issues.apache.org/jira/browse/MYFACES-4153 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.3.0-beta >Reporter: Dora Rajappan >Priority: Minor > > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group towards the left since it gets rendered as html > table. This is same behaviour for mojarra 2.2 also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYFACES-4155) For inputFile upload when multipart form is submitted the actionListener is not able to get the file.getSubmittedFileName()
Dora Rajappan created MYFACES-4155: -- Summary: For inputFile upload when multipart form is submitted the actionListener is not able to get the file.getSubmittedFileName() Key: MYFACES-4155 URL: https://issues.apache.org/jira/browse/MYFACES-4155 Project: MyFaces Core Issue Type: Bug Reporter: Dora Rajappan For inputFile upload when multipart form is submitted the actionListener is not able to get the file.getSubmittedFileName() . It throws below exception with myfaces while its passed with mojarra. Class org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper can not access a member of class org.apache.catalina.fileupload.PartItem with modifiers "public" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102) at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:296) at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:288) at java.lang.reflect.Method.invoke(Method.java:491) at org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper.getSubmittedFileName(HttpPartWrapper.java:96) at UserBean.save(UserBean.java:595) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly
[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169963#comment-16169963 ] Dora Rajappan commented on MYFACES-4154: Mojarra also has same behaviour . Chrome shows the previous page name while its at a current page. > The browser (chrome) always show the previous page name while its on the > current page rendered properly > --- > > Key: MYFACES-4154 > URL: https://issues.apache.org/jira/browse/MYFACES-4154 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Dora Rajappan >Priority: Minor > > The browser (chrome) always show the previous page name while its on the > current page rendered properly . This bug is already logged in jira not sure > of the bug id. Not sure its browser problem or jsf. Not checked this with > mojarra also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group
[ https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169731#comment-16169731 ] Thomas Andraschko commented on MYFACES-4153: Will you provide a patch? A example app would be great if not ;) > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group > --- > > Key: MYFACES-4153 > URL: https://issues.apache.org/jira/browse/MYFACES-4153 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.3.0-beta >Reporter: Dora Rajappan >Priority: Minor > > h:selectOneRadio when rendered inside h:panelGroup which is right aligned > stands out from the group towards the left since it gets rendered as html > table. This is same behaviour for mojarra 2.2 also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly
[ https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169730#comment-16169730 ] Thomas Andraschko commented on MYFACES-4154: Will you provide a patch? A example app would be great if not ;) > The browser (chrome) always show the previous page name while its on the > current page rendered properly > --- > > Key: MYFACES-4154 > URL: https://issues.apache.org/jira/browse/MYFACES-4154 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Dora Rajappan >Priority: Minor > > The browser (chrome) always show the previous page name while its on the > current page rendered properly . This bug is already logged in jira not sure > of the bug id. Not sure its browser problem or jsf. Not checked this with > mojarra also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)