[JBoss JIRA] (RFPL-3035) Clean-up/Remove the RFSBOX jira project
by Brian Leathem (JIRA)
Brian Leathem created RFPL-3035:
-----------------------------------
Summary: Clean-up/Remove the RFSBOX jira project
Key: RFPL-3035
URL: https://issues.jboss.org/browse/RFPL-3035
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: administration
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 5-Tracking
The RFSBOX jira project was made to track sandbox issues. However an entire JIRA poject is too heavy-weight for the RichFaces Sabnbox, given that it is instead a collection of independent components and never undergoes a release.
For this reason we are favoring the github issue reporter for the sandbox:
https://github.com/richfaces/richfaces-sandbox/issues
This issue covers the task of reviewing the legacy RFSBOX issues and migrating to the github jira as appropriate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RFPL-3032) Prepare RichFaces qa repository for Graphene 2.0.0.Beta1 release
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3032?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3032:
-------------------------------------
I have created a separate module under metamer-root, called metamer-ftest-legacy. This module contains all remaining Selenium 1 tests as well as all needed help-classes.
Unnecessary classes (related to Se1 tests) were removed from metamer-ftest module.
Also I have created two Jenkins jobs for testing. Once the tests are confirmed I can merge this branch.
> Prepare RichFaces qa repository for Graphene 2.0.0.Beta1 release
> ----------------------------------------------------------------
>
> Key: RFPL-3032
> URL: https://issues.jboss.org/browse/RFPL-3032
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Assignee: Matej Novotny
> Fix For: 5.0.0.Alpha2
>
>
> There will be removed support for Selenium 1 in Graphene 2.0.0.Beta1.
> The module test-ng listeners of qa repository depends on it. We need to figure out how to fix it (e.g. add there dependency for Graphene 1).
> We need to fix it before release (try it with SNAPSHOT).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RFPL-3034) Run RichFaces 5 tests with JSF 2.2
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-3034:
-----------------------------------
Summary: Run RichFaces 5 tests with JSF 2.2
Key: RFPL-3034
URL: https://issues.jboss.org/browse/RFPL-3034
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 5.0.0.Alpha1
Reporter: Pavol Pitonak
Assignee: Matej Novotny
Fix For: 5.0.0.Alpha2
Smoke-test RichFaces 5 with Mojarra 2.2. The easiest way is to run existing tests on latest WildFly 8 (now 8.0.0.Alpha4). There are two Arquillian profiles ready in richfaces-qa repository (wildfly-managed-8-0 and wildfly-remote-8-0) but Metamer itself doesn't work on WildFly.
# Fix Metamer so that it works in all containers, including WildFly 8.
# Create Jenkins job running all Metamer tests in "plain" template with WildFly 8 on Firefox (you can copy and modify job richfaces-5.0-metamer-firefox).
# Create wildfly-managed-8-0 and wildfly-remote-8-0 profiles in richfaces repository. Use pull request so that we can review changes.
# Create Jenkins job running all framework tests with PhantomJS and WildFly 8 (you can copy and modify job richfaces-5.0).
# Review all open RF issues with label "jsf22".
# Report all problems and set label to "jsf22" on them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months