January 2015 - richfaces-planning-issues

[JBoss JIRA] (RFPL-3708) Test RichFaces with JBDS 8.0.1

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3708?page=com.atlassian.jira.plugin.... ] Matej Novotny resolved RFPL-3708. --------------------------------- Resolution: Done Fourth step works too. Resolving issue. > Test RichFaces with JBDS 8.0.1 > ------------------------------ > > Key: RFPL-3708 > URL: https://issues.jboss.org/browse/RFPL-3708 > Project: RichFaces Planning > Issue Type: Sub-task > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 4.5.2.Final > > > *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' > #* 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.0.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.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3690) Change distribution and maven jars to use the same names

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3690?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3690. --------------------------------- Fix Version/s: 4.5.2.Final Resolution: Done > Change distribution and maven jars to use the same names > -------------------------------------------------------- > > Key: RFPL-3690 > URL: https://issues.jboss.org/browse/RFPL-3690 > Project: RichFaces Planning > Issue Type: Task > Affects Versions: 4.5.1.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Critical > Fix For: 4.5.2.Final > > > Productization requires that the jars from distribution have the same name as the jars on Maven. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3689) Update RF jira releases

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3689?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3689. --------------------------------- Resolution: Done > Update RF jira releases > ----------------------- > > Key: RFPL-3689 > URL: https://issues.jboss.org/browse/RFPL-3689 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3670) RichFaces 4.5.2.Final Release

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3670?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3670. --------------------------------- Resolution: Done > RichFaces 4.5.2.Final Release > ----------------------------- > > Key: RFPL-3670 > URL: https://issues.jboss.org/browse/RFPL-3670 > Project: RichFaces Planning > Issue Type: Task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.5.2.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > RichFaces version: {{4.5.2.Final}} > RichFaces tag: {{[4.5.2.Final|https://github.com/richfaces/richfaces/releases/tag/4.5.2.Final]}} > Metamer tag: {{4.5.2.20150109-Final}} > Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ > Private stage: https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > ---- > 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#ch... > [2] https://github.com/richfaces/richfaces-qa/blob/master/howto-release.adoc -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3688) Tweet and post forum announcements

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3688?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3688. --------------------------------- Resolution: Done > Tweet and post forum announcements > ---------------------------------- > > Key: RFPL-3688 > URL: https://issues.jboss.org/browse/RFPL-3688 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3686) Make project site live

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3686?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3686. --------------------------------- Resolution: Done > Make project site live > ---------------------- > > Key: RFPL-3686 > URL: https://issues.jboss.org/browse/RFPL-3686 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3687) Make blog live

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3687?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3687. --------------------------------- Resolution: Done > Make blog live > -------------- > > Key: RFPL-3687 > URL: https://issues.jboss.org/browse/RFPL-3687 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3685) Deploy the showcase

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3685?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3685. --------------------------------- Resolution: Done > Deploy the showcase > ------------------- > > Key: RFPL-3685 > URL: https://issues.jboss.org/browse/RFPL-3685 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3684) Prep announcement blog

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3684?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3684. --------------------------------- Resolution: Done > Prep announcement blog > ---------------------- > > Key: RFPL-3684 > URL: https://issues.jboss.org/browse/RFPL-3684 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3683) Prep RichFaces project site for release

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3683?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3683. --------------------------------- Resolution: Done > Prep RichFaces project site for release > --------------------------------------- > > Key: RFPL-3683 > URL: https://issues.jboss.org/browse/RFPL-3683 > Project: RichFaces Planning > Issue Type: Sub-task > Components: release > Affects Versions: 4.5.2.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues January 2015