December 2013 - richfaces-planning-issues

[JBoss JIRA] (RFPL-3034) Run RichFaces 5 tests with JSF 2.2

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-3034?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-3034: -------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > Run RichFaces 5 tests with JSF 2.2 > ---------------------------------- > > Key: RFPL-3034 > URL: https://issues.jboss.org/browse/RFPL-3034 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Smoke-test RichFaces 5 with Mojarra 2.2. The easiest way is to run existing tests on latest WildFly 8 (now 8.0.0.Alpha4). There are two Arquillian profiles ready in richfaces-qa repository (wildfly-managed-8-0 and wildfly-remote-8-0) but Metamer itself doesn't work on WildFly. > # Fix Metamer so that it works in all containers, including WildFly 8. > # Create Jenkins job running all Metamer tests in "plain" template with WildFly 8 on Firefox (you can copy and modify job richfaces-5.0-metamer-firefox). > # Create wildfly-managed-8-0 and wildfly-remote-8-0 profiles in richfaces repository. Use pull request so that we can review changes. > # Create Jenkins job running all framework tests with PhantomJS and WildFly 8 (you can copy and modify job richfaces-5.0). > # Review all open RF issues with label "jsf22". > # Report all problems and set label to "jsf22" on them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2985) RF5 Autocomplete: Initial QE Tasks

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-2985?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-2985: -------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > RF5 Autocomplete: Initial QE Tasks > ---------------------------------- > > Key: RFPL-2985 > URL: https://issues.jboss.org/browse/RFPL-2985 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Lukáš Fryč > Assignee: Pavol Pitonak > Priority: Blocker > Fix For: 5.0.0.Alpha3 > > > # review components - widget, JSF component, see demos and dev examples > # create JavaScript tests for component > # create/update Jenkins job(s) to run JavaScript tests continuously > # add component to Metamer (on feature branch as long as it is in sandbox) > # create/update page fragment if it makes sense > # create/update framework tests for component for each component's attribute and for each major feature > # create Metamer tests for those use-cases requiring templates > # review documentation - JavaDoc, VDL doc, Developer Guide, Component Reference > # update Migration Guide https://github.com/richfaces/richfaces/wiki/RichFaces-5-Migration-Guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3038) RF5 Charts: Initial QE Tasks

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-3038?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-3038: -------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > RF5 Charts: Initial QE Tasks > ---------------------------- > > Key: RFPL-3038 > URL: https://issues.jboss.org/browse/RFPL-3038 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Priority: Critical > Fix For: 5.0.0.Alpha3 > > > # review chart components > # create JavaScript tests for chart components > # create/update Jenkins job to run JavaScript tests continuously > # add chart components to Metamer (on feature branch as long as they are in sandbox) > # create page fragment if it makes sense > # create framework tests for chart components for each component's attribute and for each major feature > # create Metamer tests for those use-cases requiring templates > # review documentation - JavaDoc, VDL doc, Developer Guide, Component Reference > link all reported bugs in component to this issue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3093) Test RichFaces with JBoss Tools

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3093?page=com.atlassian.jira.plugin.... ] Juraj Húska commented on RFPL-3093: ----------------------------------- ad 1-3: it went smoothly. I have reported one small issue: JBIDE-16272 - Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion. ad 4: I will wait till the bits are released to upstream > Test RichFaces with JBoss Tools > ------------------------------- > > Key: RFPL-3093 > URL: https://issues.jboss.org/browse/RFPL-3093 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Juraj Húska > Fix For: 4.5.0.Alpha1 > > > # create a new Ant project and deploy it to JBoss AS 7 and Tomcat 7 > # create a new Maven project and deploy it to JBoss AS 7 and Tomcat 7 > # try to import existing Maven project > # create new project from JBoss Central > add 4. > According to the RFPL-2204 it should be verified that the project can be generated only from Maven Central, steps to do that: > In addition to this, a manual verification of the archetype in JBoss tools is required. Steps to test a SANPSHOT of the archetype in JBoss tools are as follows: > (03:05:35 PM) Snjeza: you can create project example user site pointing to whatever project example descriptor you want > (03:06:09 PM) bleathem: Snjeza: how do you do that? > (03:09:12 PM) Snjeza: bleathem: Call Window>Preferences>JBoss Tools>Project Examples and click the Add button. Project example xml file can be in your local file system > (03:09:53 PM) bleathem: Snjeza: and how do I make a project example xml file? Can I just copy one from somehwere else? > (03:15:10 PM) Snjeza: bleathem: you can copy the following http://download.jboss.org/jbosstools/examples/project-examples-shared-3.3... and change the version of your richfaces archetype > (03:33:58 PM) Snjeza: bleathem: You have to check the Show experimental sites checkbox if you want user sites to be shown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3076) Smoke test Showcase on OpenShift

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3076?page=com.atlassian.jira.plugin.... ] Matej Novotny resolved RFPL-3076. --------------------------------- Resolution: Done > Smoke test Showcase on OpenShift > -------------------------------- > > Key: RFPL-3076 > URL: https://issues.jboss.org/browse/RFPL-3076 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Steps to test: > # Get OpenShift account here: [https://www.openshift.com/] > # Add application, use EAP, choose public URL and such - initial app will be created and deployed. > #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. > # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. > # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] > # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder > # Commit the changes from repository folder using following commands: > #* git add -A > #* git commit -m "some message" > #* git push > # The application will deploy and you can access it using link visible under "My Applications" tab -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3076) Smoke test Showcase on OpenShift

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3076?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3076: ------------------------------------- I have deployed and tested showcase on openshift accordingly to description. The only issue I found is already filled in RF-13415. Otherwise the application renders and works correctly. > Smoke test Showcase on OpenShift > -------------------------------- > > Key: RFPL-3076 > URL: https://issues.jboss.org/browse/RFPL-3076 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Steps to test: > # Get OpenShift account here: [https://www.openshift.com/] > # Add application, use EAP, choose public URL and such - initial app will be created and deployed. > #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. > # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. > # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] > # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder > # Commit the changes from repository folder using following commands: > #* git add -A > #* git commit -m "some message" > #* git push > # The application will deploy and you can access it using link visible under "My Applications" tab -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3141) Metamer: fix styling in samples of r:status to be visible on IE browsers

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3141?page=com.atlassian.jira.plugin.... ] Jiří Štefek updated RFPL-3141: ------------------------------ Fix Version/s: 5.0.0.Alpha3 > Metamer: fix styling in samples of r:status to be visible on IE browsers > ------------------------------------------------------------------------ > > Key: RFPL-3141 > URL: https://issues.jboss.org/browse/RFPL-3141 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Fix For: 5.0.0.Alpha3 > > > The status is hidden behind the command buttons ('Send Ajax Request*') on IE browsers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3141) Metamer: fix styling in samples of r:status to be visible on IE browsers

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3141?page=com.atlassian.jira.plugin.... ] Jiří Štefek resolved RFPL-3141. ------------------------------- Resolution: Done > Metamer: fix styling in samples of r:status to be visible on IE browsers > ------------------------------------------------------------------------ > > Key: RFPL-3141 > URL: https://issues.jboss.org/browse/RFPL-3141 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Fix For: 5.0.0.Alpha3 > > > The status is hidden behind the command buttons ('Send Ajax Request*') on IE browsers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3076) Smoke test Showcase on OpenShift

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3076?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3076: ------------------------------------- Updated a link to Showcase app, former one was pointing to old version (4.3.4). > Smoke test Showcase on OpenShift > -------------------------------- > > Key: RFPL-3076 > URL: https://issues.jboss.org/browse/RFPL-3076 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Steps to test: > # Get OpenShift account here: [https://www.openshift.com/] > # Add application, use EAP, choose public URL and such - initial app will be created and deployed. > #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. > # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. > # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] > # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder > # Commit the changes from repository folder using following commands: > #* git add -A > #* git commit -m "some message" > #* git push > # The application will deploy and you can access it using link visible under "My Applications" tab -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3076) Smoke test Showcase on OpenShift

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3076?page=com.atlassian.jira.plugin.... ] Matej Novotny updated RFPL-3076: -------------------------------- Description: Steps to test: # Get OpenShift account here: [https://www.openshift.com/] # Add application, use EAP, choose public URL and such - initial app will be created and deployed. #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder # Commit the changes from repository folder using following commands: #* git add -A #* git commit -m "some message" #* git push # The application will deploy and you can access it using link visible under "My Applications" tab was: Steps to test: # Get OpenShift account here: [https://www.openshift.com/] # Add application, use EAP, choose public URL and such - initial app will be created and deployed. #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder # Commit the changes from repository folder using following commands: #* git add -A #* git commit -m "some message" #* git push # The application will deploy and you can access it using link visible under "My Applications" tab > Smoke test Showcase on OpenShift > -------------------------------- > > Key: RFPL-3076 > URL: https://issues.jboss.org/browse/RFPL-3076 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Steps to test: > # Get OpenShift account here: [https://www.openshift.com/] > # Add application, use EAP, choose public URL and such - initial app will be created and deployed. > #* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link. > # GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine. > # Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] > # Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder > # Commit the changes from repository folder using following commands: > #* git add -A > #* git commit -m "some message" > #* git push > # The application will deploy and you can access it using link visible under "My Applications" tab -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues December 2013