richfaces-planning-issues
May 2015
richfaces-planning-issues@lists.jboss.org
- 1 participants
- 143 discussions
[JBoss JIRA] (RFPL-3831) Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3831?page=com.atlassian.jira.plugin.... ]
Jiří Štefek resolved RFPL-3831.
-------------------------------
Resolution: Done
done, nothing new
> Manually smoke test Showcase with Tomcat 8 and MyFaces on tablets
> -----------------------------------------------------------------
>
> Key: RFPL-3831
> URL: https://issues.jboss.org/browse/RFPL-3831
> Project: RichFaces Planning
> Issue Type: Sub-task
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Jiří Štefek
> Fix For: 4.5.5
>
>
> 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...]).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
- 1
- 0
[JBoss JIRA] (RFPL-3833) Test RichFaces with JBDS 8.1.0
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3833?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3833:
-------------------------------------
1,2 & 3 are fine.
> Test RichFaces with JBDS 8.1.0
> ------------------------------
>
> Key: RFPL-3833
> URL: https://issues.jboss.org/browse/RFPL-3833
> Project: RichFaces Planning
> Issue Type: Sub-task
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Fix For: 4.5.5
>
>
> *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}<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 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... 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 <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.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.3.15#6346)
10 years, 11 months
- 1
- 0
[JBoss JIRA] (RFPL-3827) Test Metamer resourceMapping options on WildFly 8.2
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3827?page=com.atlassian.jira.plugin.... ]
Jiří Štefek resolved RFPL-3827.
-------------------------------
Resolution: Done
verified with job, no problems found
> Test Metamer resourceMapping options on WildFly 8.2
> ---------------------------------------------------
>
> Key: RFPL-3827
> URL: https://issues.jboss.org/browse/RFPL-3827
> Project: RichFaces Planning
> Issue Type: Sub-task
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Jiří Štefek
> Fix For: 4.5.5
>
>
> Since there are some thing which are not enough covered by ftests, have a look at various resourceMapping configurations and how it looks like live.
> Test in Metamer on latest WildFly 8.2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 12 months
- 1
- 0