Notes on the MyFaces Core 2.1.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.1.6 snapshots:


Note: Maven 2.1.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.1.4

mvn release:prepare -DdryRun=true

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

mvn release:prepare

mvn release:perform

2. Preparing core 2.1.6

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

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

mvn release:prepare -DprepareRelease=true

mvn release:perform -DperformRelease=true

4. JIRA Release Management

5. Next step is the TCK

6. Generate assembly

mvn install -Pgenerate-assembly
cd assembly
mvn package

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

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

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

cd /home/lu4242/public_html/myfaces216binsrc/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/myfaces216binsrc/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.1.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.1.4  [1]
 2. Maven artifact group "org.apache.myfaces.core" v2.1.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.1.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/myfaces216binsrc/sources
cp * /www/
cd /home/lu4242/public_html/myfaces216binsrc/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.1.6 Release

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

MyFaces Core is a JavaServer(tm) Faces 2.1 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.1.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.1.6 


    [MYFACES-3437] - [PERF] Use index-based loop where possible


    [MYFACES-3401] - Issue with RichFaces fileUpload component using MyFaces 2.0
    [MYFACES-3414] - MyFaces ResourceImpl$ValueExpressionFilterInputStream does not handle resolving long URLs
    [MYFACES-3416] - Default ValidatorFactory is not stored on application map
    [MYFACES-3429] - ArrayIndexOutOfBoundsException in CompositeELResolver under load
    [MYFACES-3430] - org.apache.myfaces.shared.resource. ResourceImpl: PushbackInputStream delegate is not closed
    [MYFACES-3431] - jsf.js: minor spec implementation bug, success is sent at the wrong location of the code
    [MYFACES-3433] - PhaseListenerManager throws NPE if pre-phase action was unsuccessful
    [MYFACES-3440] - Contents of CDATA blocks consumed in facelets-processing jspx/xml
    [MYFACES-3442] - Infinite loop when calling ApplicationImpl._handleListenerForAnnotations under heavy load
    [MYFACES-3444] - js-error: _mfInternal is null
    [MYFACES-3454] - composite component is not rendered anymore with 2.1.6-SNAPSHOT
    [MYFACES-3455] - [myfaces-2.1.6-SNAPSHOT] Using f:ajax within h:commandButton to dynamic switch ui:include works not correct anymore
    [MYFACES-3456] - jsf.jsf: Small refactoring bug in the eval code
    [MYFACES-3457] - Implicit Object Resolver for JSP does not resolve "resource" object


    [MYFACES-3266] - [perf] [concurrency] check correct logger creation
    [MYFACES-3420] - jsf.js: Another round of small bugfixes and improvements
    [MYFACES-3423] - [perf] Use ArrayList instead LinkedList in UIComponent.pushComponentToEL / popComponentFromEL
    [MYFACES-3424] - call popComponentFromEL from right instance when broadcast
    [MYFACES-3425] - [perf] enhance code applying best practices
    [MYFACES-3426] - [perf] do not call default VariableResolver / PropertyResolver when no custom instance is set
    [MYFACES-3427] - [perf] Use only one StringBuilder for generate unique facelets identifiers
    [MYFACES-3428] - [perf] optimize UILeaf
    [MYFACES-3432] - [perf] [mem] UIViewRoot.saveState(FacesContext) unnecessary saves empty view scope
    [MYFACES-3438] - jsf.js: error handling output improvement
    [MYFACES-3439] - [perf] ApplicationImpl: use cached info about ResourceDependecies for behaviors, converters and validators
    [MYFACES-3441] - [perf] use shared StringBuilder instance
    [MYFACES-3443] - [perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set
    [MYFACES-3445] - [perf] reduce HtmlResponseWriterImpl overhead
    [MYFACES-3446] - [perf] Improve html Renderers
    [MYFACES-3449] - [perf] replace buffer in PartialResponseWriter implementation with a fast filter
    [MYFACES-3450] - [perf] use grails StreamCharBuffer instead FastWriter in HtmlResponseWriterImpl
    [MYFACES-3451] - [core] Improve PSS algorithm when a dynamic view (use of c:if or ui:include src=#{...}) is used
    [MYFACES-3452] - Log managed bean creation in LifecycleProvider instances with finest level

New Feature

    [MYFACES-3418] - [perf] do not check for duplicate ids when saving view on production stage


Leonardo Uribe

CoreRelease216 (last edited 2012-02-07 14:54:17 by LeonardoUribe)