Notes on the MyFaces Core 2.0.6 Release




Here's how you can help us test the distribution.

Download a nightly build of the distribution assemblies:

Configure a <repository> for Maven 2:

           <name>Apache Snapshot Repository</name>

And declare a dependency on the 2.0.6 snapshots:


Note: Maven 2.0.6 will not download a new version if one is already present in your local repository. You will need to delete $M2_REPO/org/apache/myfaces/core to force Maven to download the new version. (Usually, $M2_REPO is <your home directory>/.m2/repository .)

Test your application, then, let us know the results (good or bad!) on dev -at- (You must be subscribed to post. See:


Proposed Release Announcement


1. Preparing shared 4.0.7

mvn release:prepare -DtagBase= -DdryRun=true

mvn release:prepare -DtagBase= -Dresume=false
mvn install
mvn release:rollback
mvn release:prepare -DtagBase= -Dresume=false

mvn release:prepare -DtagBase= 

mvn release:perform -DtagBase= 

2. Preparing core 2.0.6

mvn clean install
mvn install -Pgenerate-assembly -Papache-release
mvn release:prepare -DprepareRelease=true -DtagBase= -DdryRun=true

mvn release:prepare -DprepareRelease=true -DtagBase= -Dresume=false
mvn install
mvn install -Pgenerate-assembly -Papache-release
mvn release:rollback -DprepareRelease=true 
mvn release:prepare -DprepareRelease=true -DtagBase= -Dresume=false

mvn release:prepare -DtagBase= -DprepareRelease=true

mvn release:perform -DtagBase= -DperformRelease=true

4. JIRA Release Management

5. Next step is the TCK

6. Generate assembly

cd 2_0_4
mvn install -Pgenerate-assembly
cd assembly
mvn package

openssl md5 myfaces-core-2.0.6-src.tar.gz > myfaces-core-2.0.6-src.tar.gz.md5
openssl md5 >
openssl sha1 myfaces-core-2.0.6-src.tar.gz > myfaces-core-2.0.6-src.tar.gz.sha1
openssl sha1 >
gpg --armor --output myfaces-core-2.0.6-src.tar.gz.asc --detach-sig myfaces-core-2.0.6-src.tar.gz
gpg --armor --output --detach-sig

openssl md5 myfaces-core-2.0.6-bin.tar.gz > myfaces-core-2.0.6-bin.tar.gz.md5
openssl md5 >
openssl sha1 myfaces-core-2.0.6-bin.tar.gz > myfaces-core-2.0.6-bin.tar.gz.sha1
openssl sha1 >
gpg --armor --output myfaces-core-2.0.6-bin.tar.gz.asc --detach-sig myfaces-core-2.0.6-bin.tar.gz
gpg --armor --output --detach-sig

scp -p -r myfaces-core-2.0.6-bin*
scp -p -r myfaces-core-2.0.6-src*

cd /home/lu4242/public_html/myfaces206binsrc/binaries

wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate

cd /home/lu4242/public_html/myfaces206binsrc/sources

wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate
wget --no-check-certificate



I was running the needed tasks to get the 2.0.6 release of Apache
MyFaces core out.

The artifacts passed all TCK tests.

Please note that this vote concerns all of the following parts:
 1. Maven artifact group "org.apache.myfaces.shared" v4.0.7  [1]
 2. Maven artifact group "org.apache.myfaces.core" v2.0.6  [1]

The artifacts were deployed on nexus repo [1] and to my private 
Apache account [3] for binary and source packages.

The release notes could be found at [4].

Also the clirr test does not show binary incompatibilities with myfaces-api.

Please take a look at the "2.0.6" artifacts and vote!

Please note: This vote is "majority approval" with a minimum of three
+1 votes (see [3]).

[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
 and why..............

Leonardo Uribe


8. Clirr report to check binary incompatibilities success

9. Vote closed, starting distribution

cd /home/lu4242/public_html/myfaces206binsrc/sources
cp * /www/
cd /home/lu4242/public_html/myfaces206binsrc/binaries
cp * /www/

Alternative for manual copy:

mvn clean deploy -DaltDeploymentRepository=myfaces-staging::default::scpexe:// -Psign-artifacts -DperformRelease=true -Dpassphrase=???

Alternative for manual copy:

mvn clean deploy -DaltDeploymentRepository=myfaces-staging::default::scpexe:// -Psign-artifacts -DperformRelease=true -Dpassphrase=??? -Pgenerate-assembly 

10. Announce

Subject: [ANNOUNCE] MyFaces Core v2.0.6 Release

The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.0.6.

MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100% compliant with the JSR-314 specification. 

MyFaces Core 2.0.6 is available in both binary and source distributions.


MyFaces Core is also available in the central Maven repository under Group ID "org.apache.myfaces.core".

Release Notes - MyFaces Core - Version 2.0.6 


    * [MYFACES-3134] - Move all code related to state caching into one place
    * [MYFACES-3137] - Align ResponseStateManager implementation with the spec
    * [MYFACES-3138] - Simplify ResponseStateManager implementation code


    * [MYFACES-2924] - Component bindings are not reset when explicit navigation to the same page is derived from action
    * [MYFACES-3080] - 'begin' event does not have 'status' property set
    * [MYFACES-3100] - Repeated postbacks create additional serialized views
    * [MYFACES-3101] - NavigationHandlerImpl throws NullpointerException if view is expired
    * [MYFACES-3107] - FacesConfigurator doesn't recognize Tobago
    * [MYFACES-3108] - ResourceHandlerCache does not honor localePrefix
    * [MYFACES-3109] - UIInput SystemEvents are called with wrong sourceBaseTyp
    * [MYFACES-3114] - jsf.js jsf.ajax.response relies on internal parameters
    * [MYFACES-3115] - jsf.js event handler source id might be missing
    * [MYFACES-3116] - MyFaces cannot resolve @ManagedProperty on startup, throws UnsupportedOperationException
    * [MYFACES-3117] - Current server state saving implementation prevents multi-window usage
    * [MYFACES-3118] - jsf.js: ie9 fixes
    * [MYFACES-3125] - ValidatorTagHandlerDelegate does not invoke next handler in partial processing mode, which damages the component structure
    * [MYFACES-3131] - jsf.js:tables not rendering after ajax call in internet explorer 6
    * [MYFACES-3132] - javax.faces.context.ResponseWriterWrapper implementation is overdone
    * [MYFACES-3139] - jsf.js: various ie fixes of the final pre release testing round
    * [MYFACES-3140] - FacesMessage.VALUES is not ordered properly
    * [MYFACES-3141] - FacesMessage implements Serializable but cannot be serialized
    * [MYFACES-3142] - h:outputScript and h:outputStylesheet renderer listeners cannot implement PartialStateHolder
    * [MYFACES-3152] - javax.faces.application.StateManager default implementation for writeState and saveSerializedView needs to be implemented
    * [MYFACES-3154] - UIDebug doesn't check for existing url parameters


    * [MYFACES-1753] - Do not require to buffer the output with server-side-state-saving
    * [MYFACES-1791] - state management and multiple frames
    * [MYFACES-3111] - [PERF] Review UIData.saveDescendantComponentStates and restoreDescendantComponentStates
    * [MYFACES-3129] - [PERF] Call first getChildCount() or getFacetCount() before try to create the iterator


    * [MYFACES-3095] - Check h:button and h:link modifications.


Leonardo Uribe

CoreRelease206 (last edited 2011-05-29 21:00:57 by LeonardoUribe)