Bug 857808 - Port the commits from the 4.2.3 community branch on github
Summary: Port the commits from the 4.2.3 community branch on github
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ER1
: 2.1.0
Assignee: Marek Novotny
QA Contact: Pavol Pitonak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-17 04:50 UTC by Brian Leathem
Modified: 2012-11-30 15:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-30 15:35:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brian Leathem 2012-09-17 04:50:05 UTC
Fixes for RichFaces 4.2.3 are available on the RichFaces 4.2.3 branch on github:

Build:
https://github.com/richfaces/build/tree/release-develop/4.2.3

Components:
https://github.com/richfaces/components/tree/release-develop/4.2.3

Core:
https://github.com/richfaces/core/tree/release-develop/4.2.3

Showcase:
https://github.com/richfaces/showcase/tree/release-develop/4.2.3

The issues resolved are listed in the 4.2.3.CR1 RichFaces jira version:
https://issues.jboss.org/browse/RF/fixforversion/12320071

Porting of the individual fixes to the 4.2.3 branch was tracked via the RFPL jira issue:
https://issues.jboss.org/browse/RFPL-2349

Please merge the changes from the above linked github branches into the enterprise RichFaces repository.

Comment 2 Marek Novotny 2012-09-24 12:24:13 UTC
we have all changes in product branches

Comment 5 Pavol Pitonak 2012-09-27 15:18:27 UTC
I verified that all commits are in WFK branch and that all issues are fixed properly.

Comment 6 Isaac Rooskov 2012-10-08 02:44:21 UTC
Hi can you please fill out the Doc text field with information on the changes this encorporates from RichFaces 4.2.2 to 4.2.3. 

Thanks, 

Isaac

Comment 7 Karel Piwko 2012-11-30 15:35:07 UTC
Distributed as a part of WFK 2.1.0.GA release.


Note You need to log in before you can comment on or make changes to this bug.