Log in to follow, share, and participate in this community.
Article RichFaces 5.0 documentation user stories
RichFaces 5.0 documentation user storiesIn moving from RichFaces 3 to RichFaces 4, the documentation of the porjected fragmented, as we aimed to improve the accessibility of the docs, as well as turning towards more automated documentation generation. ...
Thread Push Components' Reference Data out of RF5 Docs
Push Components' Reference Data out of RF5 DocsHey guys, I have noticed each of the components in Component Reference contains referecen data: 3.5.2. Reference data component-type: org.richfaces.CommandLink component-class: org.rich...
RF5 docs? Do we really need Maven?Do we really need to stay with Maven build since we migrated to Asciidoc? Question: how someone should contribute (even though we have great Asciidoc) when it's incredibly hard to find the Asciidoc source for ...
Thread PickList and OrderingList added to RichFaces Widgets
PickList and OrderingList added to RichFaces WidgetsI ported the orderingList and pickList from the bootstrap sandbox project to the richfaces-widgets standalone JavaScript project. The port was non-trivial, as it required a Bootstrap v3 update. What a gr...
How to Build RichFaces 4.xThese instructions will walk through how to build the RichFaces 4 project.
Build Project Modules
Building Separated Modules
Building Whole Core Project at Once
Build Options
-DskipTests=true
...
RichFaces Git Workflow ModelRichFaces Git Workflow Model
Branches in Detail
Naming Conventions and Placing of Branches
Issue Workflows
Commiter Workflow
First-Time Contributor - fork and clone the repositories
Contributor W...
Article Guide to use pull requests with GitHub and JIRA
Guide to use pull requests with GitHub and JIRARichFaces JIRA is using a Git-enabled workflow which have been introduced in order to support GitHub pull requests. This JIRA workflow satisfies that each patch (pull request) will be integrated into codebase....
RichFaces 5.0 build redesignThe current RichFaces build structure (RichFaces 4.0 Build & Directory Structure) has served the project well over the initial 4.0 release, and the subsequient 4.1 and 4.2 releases, we want to re-visit the the bui...
RichFaces 5.0.0.Alpha1 has been stagedThe RichFaces 5.0.0.Alpha1 was staged to repository [1] and is available for QE. [1] https://repository.jboss.org/nexus/content/groups/staging/
Thread Single Jira versions for micro releases - good or bad?
Single Jira versions for micro releases - good or bad?For the past couple of RichFaces micro releases (4.3.2, and 4.3.1) I've used a single version in jira for both the CR and Final releases. How has this worked for people? From a version history perspective,...
RichFaces with Mojarra 2.2Hi, last week I tested RichFaces 4.3.0.Final with JSF 2.2. Since I couldn't find MyFaces 2.2, I tested only Mojarra 2.2.0-m08. There is a bug in Mojarra 2.2.0-m08 (and m09) [1] that prevents deployment of appl...
Is RichFaces 5 BOM Unnecessary?As of RichFaces 5, Maven users will need to provide just org.richfaces:richfaces:jar dependency in their POM. This dependency will bring other (mandatory) dependencies transitively: guava, cssparser, sac. ...
Thread RichFaces 4.3.2.Final release train has begun
RichFaces 4.3.2.Final release train has begunThe release jira: https://issues.jboss.org/browse/RFPL-2891 The release rapid board: https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=221 The release process for 4.3.2.Final has begun. Furth...
RichFaces 5 distribution zipHi, I have several questions about RF5 distribution zip. Distribution release 5.0.0-SNAPSHOT is being deployed to the Maven repository because our main Jenkins job uses profile "release" (we need to d...
Showcase on Openshift keeps failingHello all, The Openshift showcase is repeatedly failing. We have a monitor set up (uptimerobot.com) which notifies us when it fails, but it's failing frequently. Here is the outage report for the ...
Thread Moving the component sources to own Java packages
Moving the component sources to own Java packagesI have refactored all component related sources to respective packages. Right now we have separated those under single package org.richfaces.ui where each logical group has its own subpackage: https://...