[JBoss JIRA] (RFPL-4075) Test RichRates
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-4075:
-----------------------------------
Summary: Test RichRates
Key: RFPL-4075
URL: https://issues.jboss.org/browse/RFPL-4075
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Pavol Pitonak
Assignee: Pavol Pitonak
Priority: Minor
Fix For: 4.5.10
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.4.11#64026)
8 years, 6 months
[JBoss JIRA] (RFPL-4072) Test RichFaces with JBDS 9.0.0
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-4072:
-----------------------------------
Summary: Test RichFaces with JBDS 9.0.0
Key: RFPL-4072
URL: https://issues.jboss.org/browse/RFPL-4072
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Pavol Pitonak
Assignee: Pavol Pitonak
Fix For: 4.5.10
*In case of any changes and/or inaccuracy be sure to update this description.*
Use latest stable JBDS, e.g. for this release *9.0.0* downloaded from this site https://www.jboss.org/products/devstudio/download/
# create a new Maven project and deploy it to WildFly 9.0 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 9.0 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}<welcome-file-list>
<welcome-file>faces/index.xhtml</welcome-file>
</welcome-file-list>{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 you 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 <stacksId>richfaces-archetype-kitchensink</stacksId> and <stacksType>richfaces-kitchensink</stacksType>
#** 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)
8 years, 6 months
[JBoss JIRA] (RFPL-4071) Verify archetypes
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-4071:
-----------------------------------
Summary: Verify archetypes
Key: RFPL-4071
URL: https://issues.jboss.org/browse/RFPL-4071
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Pavol Pitonak
Assignee: Jiří Štefek
Fix For: 4.5.10
* simpleapp on mobile
{code}mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-simpleapp -DarchetypeVersion=4.5.10.Final -DgroupId=org.richfaces.test -DartifactId=simpleapp-test -Denterprise=false -Dmobile-optimized=true{code}
* kitchensink on mobile
{code}mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.5.10.Final -DgroupId=org.richfaces.test -DartifactId=kitchensink-test -Denterprise=false{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (RFPL-4073) Smoke test Showcase on OpenShift 2
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-4073:
-----------------------------------
Summary: Smoke test Showcase on OpenShift 2
Key: RFPL-4073
URL: https://issues.jboss.org/browse/RFPL-4073
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Pavol Pitonak
Assignee: Pavol Pitonak
Fix For: 4.5.10
Steps to test:
# Get OpenShift account here: [https://www.openshift.com/]
# Add application, use EAP, choose public URL and such - initial app will be created and deployed.
#* Should you need to create a SSH key follow [this|https://help.github.com/articles/generating-ssh-keys] link.
# GIT repository was created and is accessible, link is visible via "My Applications" tab - copy it to your local machine.
# Obtain a .war file of the Showcase application [here|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...]
# Go to GIT repo and delete pom.xml file (initial project will not be build then) and copy .war file into deployment folder
# Commit the changes from repository folder using following commands:
#* git add -A
#* git commit -m "some message"
#* git push
# The application will deploy and you can access it using link visible under "My Applications" tab
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.4.11#64026)
8 years, 6 months
[JBoss JIRA] (RFPL-4060) Update and review any new components attributes in Metamer
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-4060:
-----------------------------------
Summary: Update and review any new components attributes in Metamer
Key: RFPL-4060
URL: https://issues.jboss.org/browse/RFPL-4060
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Jiří Štefek
Assignee: Jiří Štefek
Fix For: 4.5.10
# update all *Attributes* files in Metamer running {{mvn test -Pupdate-attributes}} in *metamer/ftest*
# if there are any changes ({{git status}}), review them whether there is a relevant modification in RichFaces framework (in resolved issues) or it was an unwanted side effect of some fix. Then commit the expected changes or report a bug. (or do nothing, when there are no changes)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months