[ANNOUNCE] MyFaces Core v2.0.17 Release

[Leonardo Uribe <lu...@apache.org>]

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

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.17 is available in both binary and source distributions.

    * http://myfaces.apache.org/download.html

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

Release Notes - MyFaces Core - Version 2.0.17

Bug

    [MYFACES-3659] - Conditional include of scripts and stylesheets
    [MYFACES-3660] - Component resource added using
@ResourceDependency annotation from a facelet component should have an
id defined by facelets
    [MYFACES-3663] - UIViewRoot.createUniqueId() should generate
unique ids for all the component tree.
    [MYFACES-3665] - f:metadata section removed when refresh view and
is not included in the template directly
    [MYFACES-3666] - IE8 with XHR turned off fails on Ajax cycle
    [MYFACES-3668] - CLONE - UIForm.createUniqueId should take into
account prependId logic
    [MYFACES-3671] - jsf-uncompressed.js contains 'import' of not
existing file '_FinalizeableObj.js'
    [MYFACES-3695] - 'Cannot set header. Response already committed.'
on WebSphere Application Server 7 and 8
    [MYFACES-3696] - Button rendering itself after ajax request loses
type and other attributes
    [MYFACES-3697] - Error while parsing Facelet-Lib hides the real
reason when logging
    [MYFACES-3698] - h:body onload and onunload attributes rendered
twice if optimization enabled
    [MYFACES-3699] - Attribute updates targeting the event handlers
fail to work when 'this' or 'return' keywords are used
    [MYFACES-3700] - Boolean attributes not updated properly
    [MYFACES-3703] - @FacesRenderer does not seem to properly take
renderKitId into account

Improvement

    [MYFACES-3672] - TODO 'optimize this code' in
ResourceHandlerImpl.isResourceIdentifierExcluded()

regards,

Leonardo Uribe