From issues at jboss.org Tue Sep 1 05:07:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 05:07:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3985) Manually test Metamer with WildFly 8.2 and Mojarra on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3985. ------------------------------- Resolution: Done Done, nothing new. > Manually test Metamer with WildFly 8.2 and Mojarra on IE11 > ---------------------------------------------------------- > > Key: RFPL-3985 > URL: https://issues.jboss.org/browse/RFPL-3985 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 05:22:05 2015 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 1 Sep 2015 05:22:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3997) Test RichRates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RFPL-3997. --------------------------------- Resolution: Done > Test RichRates > -------------- > > Key: RFPL-3997 > URL: https://issues.jboss.org/browse/RFPL-3997 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Priority: Minor > Fix For: 4.5.9 > > > You can find latest version of RichRates in https://github.com/ppitonak/richrates > It's sufficient to change version of RichFaces in pom.xml to the current release's version and run all automated tests in Firefox and PhantomJS using > {code} > mvn clean verify -P wildfly-managed-8-2,all-tests > mvn clean verify -P wildfly-managed-8-2,all-tests -D arq.extension.webdriver.browser=phantomjs > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 05:38:06 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 05:38:06 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3986) Manually test Metamer with WildFly 9.0 and Mojarra on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3986. ------------------------------- Resolution: Done Done, nothing new. > Manually test Metamer with WildFly 9.0 and Mojarra on Chrome > ------------------------------------------------------------ > > Key: RFPL-3986 > URL: https://issues.jboss.org/browse/RFPL-3986 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:20:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:20:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3987) Manually test Metamer with Tomcat 8 and Mojarra on IE10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3987. ------------------------------- Resolution: Done done, nothing new. > Manually test Metamer with Tomcat 8 and Mojarra on IE10 > ------------------------------------------------------- > > Key: RFPL-3987 > URL: https://issues.jboss.org/browse/RFPL-3987 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:34:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:34:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3988) Test Metamer resourceMapping options on WildFly 8.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3988. ------------------------------- Resolution: Done Done, unstable configurations/tests (push) were verified manually. > Test Metamer resourceMapping options on WildFly 8.2 > --------------------------------------------------- > > Key: RFPL-3988 > URL: https://issues.jboss.org/browse/RFPL-3988 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Run and review results of job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/Release/job/richfaces-release-metamer-resourceMapping-matrix/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:34:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:34:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3992) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3992: ------------------------------ Description: Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded ([search link|https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29]). (was: Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded ([search link|https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.8%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29]).) > Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets > ----------------------------------------------------------------- > > Key: RFPL-3992 > URL: https://issues.jboss.org/browse/RFPL-3992 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded ([search link|https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29]). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:35:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:35:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3996) Verify and close resolved issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3996: ------------------------------ Description: Verify fixed bugs and close Jira. https://issues.jboss.org/browse/RF-11842?jql=project%20%3D%20RF%20AND%20status%20%3D%20Resolved%20AND%20resolution%20in%20%28Done%2C%20%22Partially%20Completed%22%29%20AND%20fixVersion%20%3D%204.5.9%20ORDER%20BY%20key%20ASC was: Verify fixed bugs and close Jira. https://issues.jboss.org/browse/RF-13861?jql=project%20%3D%20RF%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20%3D%204.5.9%20ORDER%20BY%20key%20ASC > Verify and close resolved issues > -------------------------------- > > Key: RFPL-3996 > URL: https://issues.jboss.org/browse/RFPL-3996 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Verify fixed bugs and close Jira. > https://issues.jboss.org/browse/RF-11842?jql=project%20%3D%20RF%20AND%20status%20%3D%20Resolved%20AND%20resolution%20in%20%28Done%2C%20%22Partially%20Completed%22%29%20AND%20fixVersion%20%3D%204.5.9%20ORDER%20BY%20key%20ASC -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:36:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:36:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3992) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3992: ------------------------------ Description: Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29 was:Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded ([search link|https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29]). > Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets > ----------------------------------------------------------------- > > Key: RFPL-3992 > URL: https://issues.jboss.org/browse/RFPL-3992 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded > https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:48:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:48:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3964) Review document updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3964: ------------------------------ Description: https://issues.jboss.org/browse/RF-14060?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc (was: https://issues.jboss.org/browse/RF-14060?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20fixVersion%20%3D%204.5.8%20AND%20component%20%3D%20doc) > Review document updates > ----------------------- > > Key: RFPL-3964 > URL: https://issues.jboss.org/browse/RFPL-3964 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > https://issues.jboss.org/browse/RF-14060?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Sep 1 06:59:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 1 Sep 2015 06:59:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3964) Review document updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3964: ------------------------------ Description: https://issues.jboss.org/browse/RF-14131?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc (was: https://issues.jboss.org/browse/RF-14060?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc) > Review document updates > ----------------------- > > Key: RFPL-3964 > URL: https://issues.jboss.org/browse/RFPL-3964 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > https://issues.jboss.org/browse/RF-14131?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 03:15:06 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 03:15:06 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3984) Configure and fire automated build for Showcase in Jenkins in HTTPS setup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3984. --------------------------------- Resolution: Done HTTPS Jenkins job passed correctly. Resolving issue. > Configure and fire automated build for Showcase in Jenkins in HTTPS setup > ------------------------------------------------------------------------- > > Key: RFPL-3984 > URL: https://issues.jboss.org/browse/RFPL-3984 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 03:28:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 03:28:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3989) Manually test Showcase with WildFly 9.0 and Mojarra on Firefox In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3989. --------------------------------- Resolution: Done Verified, resolving issue. > Manually test Showcase with WildFly 9.0 and Mojarra on Firefox > -------------------------------------------------------------- > > Key: RFPL-3989 > URL: https://issues.jboss.org/browse/RFPL-3989 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 03:48:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 03:48:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3995) Smoke test Showcase on OpenShift 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3995. --------------------------------- Resolution: Done Verified, resolving issue. > Smoke test Showcase on OpenShift 2 > ---------------------------------- > > Key: RFPL-3995 > URL: https://issues.jboss.org/browse/RFPL-3995 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > > 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/richfaces/examples/richfaces-showcase/4.3.4.Final/richfaces-showcase-4.3.4.Final-openshift.war] > # 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 > NOTE: Sometimes during push there might be a failure (error in demultiplexer, app gear wont be able to restart). This is *not* connected to Showcase or RichFaces, its rather a problem with small gear (not being sufficient) or openshift or corrupted git repo. Simpliest solution is to delete the application and repeat the whole process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 04:41:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 04:41:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3993) Verify archetypes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3993. --------------------------------- Resolution: Done Verified, resolving issue. > Verify archetypes > ----------------- > > Key: RFPL-3993 > URL: https://issues.jboss.org/browse/RFPL-3993 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > > * simpleapp on desktop > {code}mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-simpleapp -DarchetypeVersion=4.5.9.Final -DgroupId=org.richfaces.test -DartifactId=simpleapp-test -Denterprise=false -Dmobile-optimized=false{code} > * simpleapp on mobile > {code}mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-simpleapp -DarchetypeVersion=4.5.9.Final -DgroupId=org.richfaces.test -DartifactId=simpleapp-test -Denterprise=false -Dmobile-optimized=true{code} > * kitchensink on desktop and mobile > {code}mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.5.9.Final -DgroupId=org.richfaces.test -DartifactId=kitchensink-test -Denterprise=false{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 04:53:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 04:53:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3983) Configure and fire automated build for Showcase and Photoalbum in Jenkins In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3983. --------------------------------- Resolution: Done Photoalbum tests are OK - all passed. Amongst Showcase tests, there were only three failures, all of which seem more like instability than anything else. [~jstefek], I see what you did there, great job! :) > Configure and fire automated build for Showcase and Photoalbum in Jenkins > ------------------------------------------------------------------------- > > Key: RFPL-3983 > URL: https://issues.jboss.org/browse/RFPL-3983 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 05:35:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 05:35:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3990) Manually smoke test Showcase with WildFly 9.0 and Mojarra on mobile phones In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3990. --------------------------------- Resolution: Done Verified, closing issue. > Manually smoke test Showcase with WildFly 9.0 and Mojarra on mobile phones > -------------------------------------------------------------------------- > > Key: RFPL-3990 > URL: https://issues.jboss.org/browse/RFPL-3990 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 05:46:05 2015 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 3 Sep 2015 05:46:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3991) Manually smoke test Showcase with WildFly 9.0 and Mojarra on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3991. --------------------------------- Resolution: Done Verified, resolving issue. > Manually smoke test Showcase with WildFly 9.0 and Mojarra on tablets > -------------------------------------------------------------------- > > Key: RFPL-3991 > URL: https://issues.jboss.org/browse/RFPL-3991 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 05:47:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 3 Sep 2015 05:47:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3992) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104954#comment-13104954 ] Ji?? ?tefek commented on RFPL-3992: ----------------------------------- Was not possible due to RF-14133. I Will check this after respin. > Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets > ----------------------------------------------------------------- > > Key: RFPL-3992 > URL: https://issues.jboss.org/browse/RFPL-3992 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded > https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 05:47:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 3 Sep 2015 05:47:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3992) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104954#comment-13104954 ] Ji?? ?tefek edited comment on RFPL-3992 at 9/3/15 5:47 AM: ----------------------------------------------------------- Was not possible due to RF-14133. I will check this after respin. was (Author: jstefek): Was not possible due to RF-14133. I Will check this after respin. > Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets > ----------------------------------------------------------------- > > Key: RFPL-3992 > URL: https://issues.jboss.org/browse/RFPL-3992 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded > https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 06:30:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 3 Sep 2015 06:30:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3958) showcase: stabilize integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RFPL-3958: ------------------------------- There are still unstable tests for: * ITestNotifyAttributes#testShowCloseButton * ITestToolBar#testExpectedElementsArePresent (only on Tomcat) > showcase: stabilize integration tests > ------------------------------------- > > Key: RFPL-3958 > URL: https://issues.jboss.org/browse/RFPL-3958 > Project: RichFaces Planning > Issue Type: Task > Components: examples > Affects Versions: 4.5.8 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > The showcase tests are not stable, especially tests for: > * collapsiblePanel > * contextMenu > * dataTable > * editor > * inplaceInput > * inplaceSelect > * push > * progressBar > * status -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 06:30:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 3 Sep 2015 06:30:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3958) showcase: stabilize integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104970#comment-13104970 ] Ji?? ?tefek edited comment on RFPL-3958 at 9/3/15 6:29 AM: ----------------------------------------------------------- There are still some unstable tests for: * ITestNotifyAttributes#testShowCloseButton * ITestToolBar#testExpectedElementsArePresent (only on Tomcat) Reopening. was (Author: jstefek): There are still unstable tests for: * ITestNotifyAttributes#testShowCloseButton * ITestToolBar#testExpectedElementsArePresent (only on Tomcat) > showcase: stabilize integration tests > ------------------------------------- > > Key: RFPL-3958 > URL: https://issues.jboss.org/browse/RFPL-3958 > Project: RichFaces Planning > Issue Type: Task > Components: examples > Affects Versions: 4.5.8 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > The showcase tests are not stable, especially tests for: > * collapsiblePanel > * contextMenu > * dataTable > * editor > * inplaceInput > * inplaceSelect > * push > * progressBar > * status -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Sep 3 06:49:05 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 3 Sep 2015 06:49:05 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3958) showcase: stabilize integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3958. ------------------------------- Resolution: Done done > showcase: stabilize integration tests > ------------------------------------- > > Key: RFPL-3958 > URL: https://issues.jboss.org/browse/RFPL-3958 > Project: RichFaces Planning > Issue Type: Task > Components: examples > Affects Versions: 4.5.8 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > The showcase tests are not stable, especially tests for: > * collapsiblePanel > * contextMenu > * dataTable > * editor > * inplaceInput > * inplaceSelect > * push > * progressBar > * status -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Sep 7 10:56:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 7 Sep 2015 10:56:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3959) RichFaces 4.5.9.Final Release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RFPL-3959: -------------------------------- Description: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.8.20150803-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6445 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc was: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.8.20150803-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6444 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6445 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc > RichFaces 4.5.9.Final Release > ----------------------------- > > Key: RFPL-3959 > URL: https://issues.jboss.org/browse/RFPL-3959 > Project: RichFaces Planning > Issue Type: Task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.5.9 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > RichFaces version: {{4.5.9.Final}} > RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} > Metamer tag: {{4.5.8.20150803-Final}} > Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ > Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 > Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6445 > ---- > More information can be found in RichFaces 4.X release testing process document [2]. > [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config > [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 8 02:37:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 8 Sep 2015 02:37:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3996) Verify and close resolved issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3996. ------------------------------- Resolution: Done > Verify and close resolved issues > -------------------------------- > > Key: RFPL-3996 > URL: https://issues.jboss.org/browse/RFPL-3996 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Verify fixed bugs and close Jira. > https://issues.jboss.org/browse/RF-11842?jql=project%20%3D%20RF%20AND%20status%20%3D%20Resolved%20AND%20resolution%20in%20%28Done%2C%20%22Partially%20Completed%22%29%20AND%20fixVersion%20%3D%204.5.9%20ORDER%20BY%20key%20ASC -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 8 02:38:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 8 Sep 2015 02:38:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3964) Review document updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3964. ------------------------------- Resolution: Done > Review document updates > ----------------------- > > Key: RFPL-3964 > URL: https://issues.jboss.org/browse/RFPL-3964 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > https://issues.jboss.org/browse/RF-14131?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%204.5.9%20AND%20component%20%3D%20doc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 03:01:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 03:01:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3992) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3992. ------------------------------- Resolution: Done Verified with my phone with Android 5 + Chrome. Nothing new. > Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets > ----------------------------------------------------------------- > > Key: RFPL-3992 > URL: https://issues.jboss.org/browse/RFPL-3992 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > Do this task only when a MyFaces-specific bug was fixed in RichFaces or when MyFaces dependency was upgraded > https://issues.jboss.org/browse/RFPL-3599?jql=project%20in%20%28RFPL%2C%20RF%29%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%204.5.9%20AND%20%28labels%20%3D%20myfaces%20OR%20text%20~%20%22myfaces%22%29 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:14:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 07:14:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3959) RichFaces 4.5.9.Final Release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RFPL-3959: -------------------------------- Description: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.8.20150803-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6600 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc was: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.8.20150803-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6445 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc > RichFaces 4.5.9.Final Release > ----------------------------- > > Key: RFPL-3959 > URL: https://issues.jboss.org/browse/RFPL-3959 > Project: RichFaces Planning > Issue Type: Task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.5.9 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > RichFaces version: {{4.5.9.Final}} > RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} > Metamer tag: {{4.5.8.20150803-Final}} > Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ > Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 > Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6600 > ---- > More information can be found in RichFaces 4.X release testing process document [2]. > [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config > [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:25:00 2015 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 15 Sep 2015 07:25:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3959) RichFaces 4.5.9.Final Release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RFPL-3959: -------------------------------- Description: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.9.20150914-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6600 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc was: RichFaces version: {{4.5.9.Final}} RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} Metamer tag: {{4.5.8.20150803-Final}} Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6600 ---- More information can be found in RichFaces 4.X release testing process document [2]. [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc > RichFaces 4.5.9.Final Release > ----------------------------- > > Key: RFPL-3959 > URL: https://issues.jboss.org/browse/RFPL-3959 > Project: RichFaces Planning > Issue Type: Task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.5.9 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > RichFaces version: {{4.5.9.Final}} > RichFaces tag: {{[4.5.9.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.9.Final]}} > Metamer tag: {{4.5.9.20150914-Final}} > Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ > Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6514 > Archetype stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6600 > ---- > More information can be found in RichFaces 4.X release testing process document [2]. > [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#changing.jsf.config > [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:36:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 07:36:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reassigned RFPL-3994: --------------------------------- Assignee: Ji?? ?tefek (was: Matej Novotny) > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (no changes needed) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs' > #* Don't forget to use JSF 2.2 > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71 profile}} > # 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 SNAPSHOT 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.Beta1.xml 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 > *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* > 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ > 4) Alter the project-examples-shared-VERSION.xml in this way > comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 > save it > 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. > 6) Shut down JBDS > in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. > Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > 7) Start JBDS. > 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header > 9) Check show experimental sites > 10) From select box choose your site. > 11) Create RichFaces project. > 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:36:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 07:36:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3994: ------------------------------ Description: *In case of any changes and/or inaccuracy be sure to update this description.* # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs' #* Don't forget to use JSF 2.2 #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # 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 SNAPSHOT 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.Beta1.xml 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 *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ 4) Alter the project-examples-shared-VERSION.xml in this way comment lines richfaces-archetype-kitchensink and richfaces-kitchensink un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 save it 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. 6) Shut down JBDS in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. 7) Start JBDS. 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header 9) Check show experimental sites 10) From select box choose your site. 11) Create RichFaces project. 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. was: *In case of any changes and/or inaccuracy be sure to update this description.* # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (no changes needed) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs' #* Don't forget to use JSF 2.2 #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # 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 SNAPSHOT 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.Beta1.xml 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 *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ 4) Alter the project-examples-shared-VERSION.xml in this way comment lines richfaces-archetype-kitchensink and richfaces-kitchensink un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 save it 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. 6) Shut down JBDS in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. 7) Start JBDS. 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header 9) Check show experimental sites 10) From select box choose your site. 11) Create RichFaces project. 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs' > #* Don't forget to use JSF 2.2 > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71 profile}} > # 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 SNAPSHOT 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.Beta1.xml 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 > *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* > 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ > 4) Alter the project-examples-shared-VERSION.xml in this way > comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 > save it > 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. > 6) Shut down JBDS > in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. > Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > 7) Start JBDS. > 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header > 9) Check show experimental sites > 10) From select box choose your site. > 11) Create RichFaces project. > 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:40:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 07:40:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3994: ------------------------------ Description: *In case of any changes and/or inaccuracy be sure to update this description.* # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: JSF 2.2 #** use Project template: 'JSF Kickstars without libs' #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # 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 SNAPSHOT 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.Beta1.xml 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 *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ 4) Alter the project-examples-shared-VERSION.xml in this way comment lines richfaces-archetype-kitchensink and richfaces-kitchensink un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 save it 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. 6) Shut down JBDS in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. 7) Start JBDS. 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header 9) Check show experimental sites 10) From select box choose your site. 11) Create RichFaces project. 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. was: *In case of any changes and/or inaccuracy be sure to update this description.* # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs' #* Don't forget to use JSF 2.2 #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # 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 SNAPSHOT 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.Beta1.xml 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 *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ 4) Alter the project-examples-shared-VERSION.xml in this way comment lines richfaces-archetype-kitchensink and richfaces-kitchensink un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 save it 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. 6) Shut down JBDS in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. 7) Start JBDS. 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header 9) Check show experimental sites 10) From select box choose your site. 11) Create RichFaces project. 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: JSF 2.2 > #** use Project template: 'JSF Kickstars without libs' > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71 profile}} > # 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 SNAPSHOT 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.Beta1.xml 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 > *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* > 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ > 4) Alter the project-examples-shared-VERSION.xml in this way > comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 > save it > 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. > 6) Shut down JBDS > in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. > Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > 7) Start JBDS. > 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header > 9) Check show experimental sites > 10) From select box choose your site. > 11) Create RichFaces project. > 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 07:50:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 07:50:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3994: ------------------------------ Description: *In case of any changes and/or inaccuracy be sure to update this description.* Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: JSF 2.2 #** use Project template: 'JSF Kickstars without libs' #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ #* Alter the project-examples-shared-VERSION.xml in this way #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. #* Shut down JBDS #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. #* Start JBDS. #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header #* Check show experimental sites #* From select box choose your site. #* Create RichFaces project. #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. was: *In case of any changes and/or inaccuracy be sure to update this description.* # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: JSF 2.2 #** use Project template: 'JSF Kickstars without libs' #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # 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 SNAPSHOT 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.Beta1.xml 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 *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:* 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/ 4) Alter the project-examples-shared-VERSION.xml in this way comment lines richfaces-archetype-kitchensink and richfaces-kitchensink un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1 save it 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file. 6) Shut down JBDS in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories. Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. 7) Start JBDS. 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header 9) Check show experimental sites 10) From select box choose your site. 11) Create RichFaces project. 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: JSF 2.2 > #** use Project template: 'JSF Kickstars without libs' > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71 profile}} > # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central > #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ > #* Alter the project-examples-shared-VERSION.xml in this way > #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it > #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. > #* Shut down JBDS > #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. > #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > #* Start JBDS. > #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header > #* Check show experimental sites > #* From select box choose your site. > #* Create RichFaces project. > #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 08:22:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 08:22:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3994: ------------------------------ Description: *In case of any changes and/or inaccuracy be sure to update this description.* Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: {{JSF 2.2}} #** use Project template: {{JSF Kickstars without libs}} #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71}} profile # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ #* Alter the project-examples-shared-VERSION.xml in this way #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. #* Shut down JBDS #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. #* Start JBDS. #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header #* Check show experimental sites #* From select box choose your site. #* Create RichFaces project. #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. was: *In case of any changes and/or inaccuracy be sure to update this description.* Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: JSF 2.2 #** use Project template: 'JSF Kickstars without libs' #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71 profile}} # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ #* Alter the project-examples-shared-VERSION.xml in this way #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. #* Shut down JBDS #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. #* Start JBDS. #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header #* Check show experimental sites #* From select box choose your site. #* Create RichFaces project. #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: {{JSF 2.2}} > #** use Project template: {{JSF Kickstars without libs}} > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71}} profile > # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central > #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ > #* Alter the project-examples-shared-VERSION.xml in this way > #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it > #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. > #* Shut down JBDS > #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. > #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > #* Start JBDS. > #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header > #* Check show experimental sites > #* From select box choose your site. > #* Create RichFaces project. > #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 08:25:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 15 Sep 2015 08:25:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108651#comment-13108651 ] Ji?? ?tefek commented on RFPL-3994: ----------------------------------- Points 1 to 3 were done. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: {{JSF 2.2}} > #** use Project template: {{JSF Kickstars without libs}} > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71}} profile > # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central > #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ > #* Alter the project-examples-shared-VERSION.xml in this way > #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it > #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. > #* Shut down JBDS > #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. > #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > #* Start JBDS. > #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header > #* Check show experimental sites > #* From select box choose your site. > #* Create RichFaces project. > #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 10:47:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 10:47:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3965) Finalize/tag/release/upload the Final version of the documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3965. --------------------------------- Resolution: Done > Finalize/tag/release/upload the Final version of the documentation > ------------------------------------------------------------------ > > Key: RFPL-3965 > URL: https://issues.jboss.org/browse/RFPL-3965 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > > Refer to the docs: > https://github.com/richfaces/richfaces-docs/blob/4.3.x/howto-release.adoc -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 10:47:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 10:47:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3966) Generate and upload the CDK maven-based docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3966. --------------------------------- Resolution: Done > Generate and upload the CDK maven-based docs > -------------------------------------------- > > Key: RFPL-3966 > URL: https://issues.jboss.org/browse/RFPL-3966 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > > richfaces-resources-dependency-plugin -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 10:53:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 10:53:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3967) Promote verified artifacts on stage server to live repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3967. --------------------------------- Resolution: Done > Promote verified artifacts on stage server to live repo > ------------------------------------------------------- > > Key: RFPL-3967 > URL: https://issues.jboss.org/browse/RFPL-3967 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 10:53:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 10:53:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3968) Copy, and rename distribution and other download files to download server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3968. --------------------------------- Resolution: Done > Copy, and rename distribution and other download files to download server > ------------------------------------------------------------------------- > > Key: RFPL-3968 > URL: https://issues.jboss.org/browse/RFPL-3968 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > > See the following mojo for details: > https://mojo.redhat.com/docs/DOC-67793 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:04:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:04:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3969) Verify uploaded release artifacts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3969. --------------------------------- Resolution: Done > Verify uploaded release artifacts > --------------------------------- > > Key: RFPL-3969 > URL: https://issues.jboss.org/browse/RFPL-3969 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > > Run Jenkins job [1] after dev notifies QE that artifacts were copied to download server. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/Release/job/richfaces-4.5-release-verify-dist-bin -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:25:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:25:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3970) Integrate the release branch back to master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3970. --------------------------------- Resolution: Done > Integrate the release branch back to master > ------------------------------------------- > > Key: RFPL-3970 > URL: https://issues.jboss.org/browse/RFPL-3970 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:26:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:26:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3973) Prep announcement blog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3973. --------------------------------- Resolution: Done > Prep announcement blog > ---------------------- > > Key: RFPL-3973 > URL: https://issues.jboss.org/browse/RFPL-3973 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:40:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:40:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3972) Prep RichFaces project site for release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3972. --------------------------------- Resolution: Done > Prep RichFaces project site for release > --------------------------------------- > > Key: RFPL-3972 > URL: https://issues.jboss.org/browse/RFPL-3972 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:46:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:46:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3974) Deploy the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3974. --------------------------------- Resolution: Done > Deploy the showcase > ------------------- > > Key: RFPL-3974 > URL: https://issues.jboss.org/browse/RFPL-3974 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:50:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:50:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3975) Make blog live In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3975. --------------------------------- Resolution: Done > Make blog live > -------------- > > Key: RFPL-3975 > URL: https://issues.jboss.org/browse/RFPL-3975 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:50:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:50:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3976) Make project site live In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3976. --------------------------------- Resolution: Done > Make project site live > ---------------------- > > Key: RFPL-3976 > URL: https://issues.jboss.org/browse/RFPL-3976 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:58:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:58:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3977) Tweet and post forum announcements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3977. --------------------------------- Resolution: Done > Tweet and post forum announcements > ---------------------------------- > > Key: RFPL-3977 > URL: https://issues.jboss.org/browse/RFPL-3977 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Sep 15 11:59:00 2015 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Sep 2015 11:59:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3978) Update RF jira releases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RFPL-3978. --------------------------------- Resolution: Done > Update RF jira releases > ----------------------- > > Key: RFPL-3978 > URL: https://issues.jboss.org/browse/RFPL-3978 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.9 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 16 03:05:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 16 Sep 2015 03:05:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3994: ------------------------------ Description: *In case of any changes and/or inaccuracy be sure to update this description.* Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: {{JSF 2.2}} #** use Project template: {{JSF Kickstars without libs}} #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71}} profile # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ #* Alter the project-examples-shared-VERSION.xml in this way #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it #* In JBDS, Window --> Preferences --> Project Examples --> add new site, which points to the edited {{.xml}} file. #* Shut down JBDS #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. #* Start JBDS. #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header #* Check show experimental sites #* From select box choose your site. #* Create RichFaces project. #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. was: *In case of any changes and/or inaccuracy be sure to update this description.* Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{Maven Project}} #* Once prompted to choose archetype, add new repository to Catalog #** As address you are going to need the staging repo URL #* Choose simple-app from the newly added repo (e.g. with correct RF version) #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) #* Test with Wildfly #** Need to activate {{jee6}} profile # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 #* File -> New -> Other #* Select {{JSF Project}} #** use JSF environment: {{JSF 2.2}} #** use Project template: {{JSF Kickstars without libs}} #* Finish the wizard, you can install Wildfly and Tomcat servers at this point #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: #** RichBean.java #** index.xhtml #** templates (whole folder) #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) #** {code} faces/index.xhtml {code} #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} #* Test on Wildfly #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} # Try to import existing Maven project #* Make use of Showcase in RF distribution ZIP and import that #* To deploy with Tomcat no additional settings is needed #* To deploy with Wildfly tou need to activate {{jbas71}} profile # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ #* Alter the project-examples-shared-VERSION.xml in this way #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it #* In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited {{.xml}} file. #* Shut down JBDS #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. #* Start JBDS. #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header #* Check show experimental sites #* From select box choose your site. #* Create RichFaces project. #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: {{JSF 2.2}} > #** use Project template: {{JSF Kickstars without libs}} > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71}} profile > # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central > #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ > #* Alter the project-examples-shared-VERSION.xml in this way > #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it > #* In JBDS, Window --> Preferences --> Project Examples --> add new site, which points to the edited {{.xml}} file. > #* Shut down JBDS > #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. > #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > #* Start JBDS. > #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header > #* Check show experimental sites > #* From select box choose your site. > #* Create RichFaces project. > #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 16 03:25:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 16 Sep 2015 03:25:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3994) Test RichFaces with JBDS 8.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3994. ------------------------------- Resolution: Done > Test RichFaces with JBDS 8.1.0 > ------------------------------ > > Key: RFPL-3994 > URL: https://issues.jboss.org/browse/RFPL-3994 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Ji?? ?tefek > Fix For: 4.5.9 > > > *In case of any changes and/or inaccuracy be sure to update this description.* > Use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/ > # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{Maven Project}} > #* Once prompted to choose archetype, add new repository to Catalog > #** As address you are going to need the staging repo URL > #* Choose simple-app from the newly added repo (e.g. with correct RF version) > #* Test with Tomcat (change RichBean from {{ViewScoped}} to {{SessionScoped}} -- JAVASERVERFACES-3400) > #* Test with Wildfly > #** Need to activate {{jee6}} profile > # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8 > #* File -> New -> Other > #* Select {{JSF Project}} > #** use JSF environment: {{JSF 2.2}} > #** use Project template: {{JSF Kickstars without libs}} > #* Finish the wizard, you can install Wildfly and Tomcat servers at this point > #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project > #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there > #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure: > #** RichBean.java > #** index.xhtml > #** templates (whole folder) > #* Add following to the web.xml (it only maps index page to localhost:8080/app_name) > #** {code} > faces/index.xhtml > {code} > #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}} > #* Test on Wildfly > #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat > #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400 > #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}} > # Try to import existing Maven project > #* Make use of Showcase in RF distribution ZIP and import that > #* To deploy with Tomcat no additional settings is needed > #* To deploy with Wildfly tou need to activate {{jbas71}} profile > # After RichFaces are in maven central repository (RFPL-2204), create new project from JBoss Central > #* Download {{project-examples-shared-VERSION.xml}} with the biggest version number from http://download.jboss.org/jbosstools/examples/ > #* Alter the project-examples-shared-VERSION.xml in this way > #** comment lines richfaces-archetype-kitchensink and richfaces-kitchensink > #** un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part). > #** change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.9.Final and save it > #* In JBDS, Window --> Preferences --> Project Examples --> add new site, which points to the edited {{.xml}} file. > #* Shut down JBDS > #** in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So any project will be built only from Maven central repositories. > #** Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary. > #* Start JBDS. > #* In JBoss Central (the start page), click on the Project Examples Wizard, located next to Start from sample header > #* Check show experimental sites > #* From select box choose your site. > #* Create RichFaces project. > #* It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 07:05:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 07:05:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: Ji?? ?tefek created RFPL-3998: --------------------------------- Summary: AjaxHalter does not work correctly with MyFaces Key: RFPL-3998 URL: https://issues.jboss.org/browse/RFPL-3998 Project: RichFaces Planning Issue Type: Enhancement Components: QE Affects Versions: 4.5.9 Environment: Metamer, AjaxHalter Reporter: Ji?? ?tefek Assignee: Pavol Pitonak The method {{continueToPhaseAfter().opened()}}, in expression: {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request, not just continue to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 07:05:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 07:05:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reassigned RFPL-3998: --------------------------------- Assignee: Ji?? ?tefek (was: Pavol Pitonak) > AjaxHalter does not work correctly with MyFaces > ----------------------------------------------- > > Key: RFPL-3998 > URL: https://issues.jboss.org/browse/RFPL-3998 > Project: RichFaces Planning > Issue Type: Enhancement > Components: QE > Affects Versions: 4.5.9 > Environment: Metamer, AjaxHalter > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > The method {{continueToPhaseAfter().opened()}}, in expression: > {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request, not just continue to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 07:07:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 07:07:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3998: ------------------------------ Description: The method {{continueToPhaseAfter().opened()}}, in expression: {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request instead of processing to the selected phase, when using MyFaces. was: The method {{continueToPhaseAfter().opened()}}, in expression: {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request, not just continue to the selected phase, when using MyFaces. > AjaxHalter does not work correctly with MyFaces > ----------------------------------------------- > > Key: RFPL-3998 > URL: https://issues.jboss.org/browse/RFPL-3998 > Project: RichFaces Planning > Issue Type: Enhancement > Components: QE > Affects Versions: 4.5.9 > Environment: Metamer, AjaxHalter > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > The method {{continueToPhaseAfter().opened()}}, in expression: > {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request instead of processing to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 07:08:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 07:08:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3998: ------------------------------ Labels: myfaces (was: ) > AjaxHalter does not work correctly with MyFaces > ----------------------------------------------- > > Key: RFPL-3998 > URL: https://issues.jboss.org/browse/RFPL-3998 > Project: RichFaces Planning > Issue Type: Enhancement > Components: QE > Affects Versions: 4.5.9 > Environment: Metamer, AjaxHalter > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > The method {{continueToPhaseAfter().opened()}}, in expression: > {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request instead of processing to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 07:08:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 07:08:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3998: ------------------------------ Issue Type: Bug (was: Enhancement) > AjaxHalter does not work correctly with MyFaces > ----------------------------------------------- > > Key: RFPL-3998 > URL: https://issues.jboss.org/browse/RFPL-3998 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Environment: Metamer, AjaxHalter > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > The method {{continueToPhaseAfter().opened()}}, in expression: > {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request instead of processing to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:34:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:34:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: Ji?? ?tefek created RFPL-3999: --------------------------------- Summary: TestJSF22FlowScopedAnnotation does not work with MyFaces Key: RFPL-3999 URL: https://issues.jboss.org/browse/RFPL-3999 Project: RichFaces Planning Issue Type: Bug Components: QE Affects Versions: 4.5.9 Reporter: Ji?? ?tefek Assignee: Ji?? ?tefek Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: {code} // go to previous page, verify second tab is active, go to next page Graphene.guardHttp(previousPageButton).click(); Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:35:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:35:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3999: ------------------------------ Description: Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: {code} // go to previous page, verify second tab is active, go to next page Graphene.guardHttp(previousPageButton).click(); Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line {code} Test can be invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} was: Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: {code} // go to previous page, verify second tab is active, go to next page Graphene.guardHttp(previousPageButton).click(); Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line {code} > TestJSF22FlowScopedAnnotation does not work with MyFaces > -------------------------------------------------------- > > Key: RFPL-3999 > URL: https://issues.jboss.org/browse/RFPL-3999 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. > The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: > {code} > // go to previous page, verify second tab is active, go to next page > Graphene.guardHttp(previousPageButton).click(); > Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line > {code} > Test can be invoked by: > {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:35:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:35:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3999: ------------------------------ Summary: metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces (was: TestJSF22FlowScopedAnnotation does not work with MyFaces) > metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces > ----------------------------------------------------------------- > > Key: RFPL-3999 > URL: https://issues.jboss.org/browse/RFPL-3999 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. > The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: > {code} > // go to previous page, verify second tab is active, go to next page > Graphene.guardHttp(previousPageButton).click(); > Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line > {code} > Test can be invoked by: > {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} (from metamer ftest) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:35:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:35:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3999: ------------------------------ Description: Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: {code} // go to previous page, verify second tab is active, go to next page Graphene.guardHttp(previousPageButton).click(); Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line {code} Test can be invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} (from metamer ftest) was: Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: {code} // go to previous page, verify second tab is active, go to next page Graphene.guardHttp(previousPageButton).click(); Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line {code} Test can be invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} > TestJSF22FlowScopedAnnotation does not work with MyFaces > -------------------------------------------------------- > > Key: RFPL-3999 > URL: https://issues.jboss.org/browse/RFPL-3999 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. > The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: > {code} > // go to previous page, verify second tab is active, go to next page > Graphene.guardHttp(previousPageButton).click(); > Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line > {code} > Test can be invoked by: > {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} (from metamer ftest) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:36:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:36:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3998) metamer: AjaxHalter does not work correctly with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3998: ------------------------------ Summary: metamer: AjaxHalter does not work correctly with MyFaces (was: AjaxHalter does not work correctly with MyFaces) > metamer: AjaxHalter does not work correctly with MyFaces > -------------------------------------------------------- > > Key: RFPL-3998 > URL: https://issues.jboss.org/browse/RFPL-3998 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Environment: Metamer, AjaxHalter > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > The method {{continueToPhaseAfter().opened()}}, in expression: > {{HaltedRequest req = halter.nextRequest().continueToPhaseAfter().opened();}} will complete the request instead of processing to the selected phase, when using MyFaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:42:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:42:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113795#comment-13113795 ] Ji?? ?tefek commented on RFPL-3999: ----------------------------------- disabled the test when using MyFaces Test can be now invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation -Dconfigurator.skip.reverse=true}} > metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces > ----------------------------------------------------------------- > > Key: RFPL-3999 > URL: https://issues.jboss.org/browse/RFPL-3999 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. > The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: > {code} > // go to previous page, verify second tab is active, go to next page > Graphene.guardHttp(previousPageButton).click(); > Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line > {code} > Test can be invoked by: > {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} (from metamer ftest) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Sep 30 09:43:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 30 Sep 2015 09:43:00 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3999) metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113795#comment-13113795 ] Ji?? ?tefek edited comment on RFPL-3999 at 9/30/15 9:42 AM: ------------------------------------------------------------ disabled the test when using MyFaces Test can be now invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation -Dconfigurator.skip.reverse=true}} (from metamer/ftest) was (Author: jstefek): disabled the test when using MyFaces Test can be now invoked by: {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation -Dconfigurator.skip.reverse=true}} > metamer: TestJSF22FlowScopedAnnotation does not work with MyFaces > ----------------------------------------------------------------- > > Key: RFPL-3999 > URL: https://issues.jboss.org/browse/RFPL-3999 > Project: RichFaces Planning > Issue Type: Bug > Components: QE > Affects Versions: 4.5.9 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Labels: myfaces > > Test {{TestJSF22FlowScopedAnnotation}} does not work with MyFaces. > The FlowScoped bean is reinitialized (the tab panel is switched back to first tab) after returning to the first page: > {code} > // go to previous page, verify second tab is active, go to next page > Graphene.guardHttp(previousPageButton).click(); > Graphene.waitGui().until().element(tabPanel.advanced().getActiveHeaderElement()).text().contains("Second tab");// fails on this line > {code} > Test can be invoked by: > {{mvn clean verify -Dbrowser=ff -Dmyfaces=true -Ptomcat-managed-8 -Dtest=TestJSF22FlowScopedAnnotation}} (from metamer ftest) -- This message was sent by Atlassian JIRA (v6.4.11#64026)