Notes on the MyFaces Core 2.0.0-beta-3 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.0-beta-3 snapshots:


Note: Maven 2.0.4 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.1 Preparing test 1.0.0-beta-2

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=1_0_0_beta_2 -DdryRun=true

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=1_0_0_beta_2 -Dresume=false

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=1_0_0_beta_2 -Dresume=false

1.2 Preparing shared 4.0.1-beta-3

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=4_0_1_beta_3 -DdryRun=true

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=4_0_1_beta_3 -Dresume=false

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=4_0_1_beta_3 -Dresume=false

2. Preparing core 2.0.0-beta-3

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=2_0_0_beta_3 -DdryRun=true

mvn release:prepare -DtagBase= -Dusername=lu4242 -Dscm.password=??? -Dtag=2_0_0_beta_3 -Dresume=false

3. Deploy on local repo

mvn clean deploy -DperformRelease=true -DaltDeploymentRepository=myfaces-local-staging::default::scp://localhost/home/lu4242/stage/repo200beta3 -Psign-artifacts -Dpassphrase=??? 

   cd home/lu4242/stage/repo200beta3
   scp -p -r org

4. JIRA Release Management

5. Next step is the TCK

6. Generate assembly

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

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

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

scp -p -r myfaces-core-2.0.0-beta-3-bin*
scp -p -r myfaces-core-2.0.0-beta-3-src*



I was running the needed tasks to get the 2.0.0-beta-3 release of Apache
MyFaces core out.

Please note that this vote concerns all of the following parts:
 1. Maven artifact group "org.apache.myfaces.shared" v4.0.1-beta-3  [1]
 2. Maven artifact group "org.apache.myfaces.core" v2.0.0-beta-3  [1]
 3. Maven artifact group "org.apache.myfaces.test" v1.0.0-beta-2 [1]

The artifacts are deployed to my private Apache account ([1] and [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.0-beta-3" 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/myfaces200beta3binsrc/sources
cp * /www/
cd /home/lu4242/public_html/myfaces200beta3binsrc/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=???

10. Announce

Subject: [ANNOUNCE] MyFaces Core v2.0.0-beta-3 Release

The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.0.0-beta-3.

MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by JSR-314. 

MyFaces Core 2.0.0-beta-3 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.0-beta-3


    * [MYFACES-2529] - use of view-param in faces-config causes a NoSuchMethodExcepion for addViewParam
    * [MYFACES-2536] - converterId and validatorId should not be required
    * [MYFACES-2543] - Facelets Taglib jars are not recognized
    * [MYFACES-2555] - org.apache.myfaces.config.annotation.LifecycleProvider context parameter is ignored
    * [MYFACES-2560] - Known class name for EL RI's ExpressionFactoryImpl is wrong
    * [MYFACES-2561] - StackOverflowError if a composite component implementation uses another composite component
    * [MYFACES-2563] - Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2
    * [MYFACES-2564] - facelets in an app with a 1.2 level faces-config do not work
    * [MYFACES-2565] - BeanValidator throws Exception if external ExpressionLanguageFactory is being used
    * [MYFACES-2567] - Log indicates Tomahawk starting even if Tomahawk is not on the classpath
    * [MYFACES-2569] - setResourceHandler, setViewHandler and setStateManager must throw illegalStateException if called after at least one request has been processed by the Lifecycle instance
    * [MYFACES-2570] - FaceletVDL.retargetMethodExpressions() should use ActionSource2 instead of ActionSource
    * [MYFACES-2571] - converter, validator and actionListener tags nested in a composite component without a for attribute should throw a TagException
    * [MYFACES-2572] - MyFaces should release the "dummy" FacesContext created during startup/shutdown
    * [MYFACES-2573] - NavigationHandler decoration/delegation not supported in 2.0.0-beta2
    * [MYFACES-2574] - InterfaceHandler stores the componentType as the resolved value instead of the ValueExpression
    * [MYFACES-2577] - Multiple client behaviors confuse the jsf.util.chain function
    * [MYFACES-2578] - When using ui:repeat and inputText with attributes that are 'nullable' (for example date attributes) they cannot be set to null by entering an empty String ("")
    * [MYFACES-2580] - OSGi: Missing javax.validation imports in api module manifest
    * [MYFACES-2581] - double slash breaks new prefix mapping (/faces//faces/*) - CTS failure
    * [MYFACES-2583] - f:ajax cannot retrieve clientId from component
    * [MYFACES-2591] - buildBehaviorChain() should also check the ClientBehaviors for the second eventName for submitting
    * [MYFACES-2592] - UIViewParameter.decode() should set the submitted value only if it is not null
    * [MYFACES-2593] - styles are escaped so that @import *.css doesn't work
    * [MYFACES-2598] - UIViewParameter does not get an automatic id
    * [MYFACES-2600] - @PostConstruct does not work
    * [MYFACES-2601] - java.lang.NoSuchFieldException when MyFaces and Mojarra are on the classpath
    * [MYFACES-2603] - Incorrect web-facesconfig_2_0.xsd
    * [MYFACES-2605] - java.lang.LinkageError loader constraint violation: loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) previously initiated loading for a different type with name "javax/el/ExpressionFactory"
    * [MYFACES-2608] - f:event type="preRenderView" not resolved
    * [MYFACES-2609] - f:event type throws ClassNotFoundException for type 'preRenderView'
    * [MYFACES-2610] - h:link not being rendered correctly when disabled - no value shown
    * [MYFACES-2611] - UIComponentBase.getFacetsAndChildren() must not access the component's facets and children directly
    * [MYFACES-2613] - ExternalSpecifications has an import from javax.validation api, and this one should be optional
    * [MYFACES-2614] - EnumConverter uses toString() instead of name()


    * [MYFACES-2559] - Google App Engine Support for Myfaces 2
    * [MYFACES-2575] - Replace RequestMap with FacesContext.getAttributes() where possible

New Feature

    * [MYFACES-2579] - Support the dynamic adding of servlets and servlet-mappings on Servlet API 3.0 to make web.xml entries for Faces Servlet not mandatory


    * [MYFACES-2568] - Panel created to hold resource on UIViewRoot is transient
    * [MYFACES-2607] - Ugly NPE in CompositeFunctionMapper.resolveFunction() if second FunctionMapper is null


Leonardo Uribe

CoreRelease200beta3 (last edited 2010-03-26 16:05:43 by LeonardoUribe)