I've done some simple testing and the release looks good
+1

Regards
Bill Lucy

On Fri, Mar 2, 2018 at 9:19 AM, Eduardo B <ebre...@gmail.com> wrote:

> +1
>
> Eduardo M. Breijo
>
> On Fri, Mar 2, 2018 at 5:10 AM, Udo Schnurpfeil <lof...@apache.org> wrote:
>
>> +1
>>
>> Regards,
>>
>> Udo
>>
>> Am 27.02.18 um 16:22 schrieb Paul Nicolucci:
>>
>> +1
>>
>> Thanks,
>>
>> Paul Nicolucci
>>
>>
>> [image: Inactive hide details for Thomas Andraschko ---02/26/2018
>> 06:04:03 PM---Ok, but as ManagedBeans are deprecated, it also fails w]Thomas
>> Andraschko ---02/26/2018 06:04:03 PM---Ok, but as ManagedBeans are
>> deprecated, it also fails with older MF versions and it's probably relat
>>
>> From: Thomas Andraschko <andraschko.tho...@gmail.com>
>> <andraschko.tho...@gmail.com>
>> To: MyFaces Development <dev@myfaces.apache.org> <dev@myfaces.apache.org>
>> Date: 02/26/2018 06:04 PM
>> Subject: Re: [VOTE] release of MyFaces Core 2.3.0
>> ------------------------------
>>
>>
>>
>> Ok, but as ManagedBeans are deprecated, it also fails with older MF
>> versions and it's probably related to Jetty -> it's no blocker. I will
>> create a separate topic for this issue.
>>
>> +1 - build is fine, rat is fine, all my other tests are fine.
>>
>> 2018-02-26 23:46 GMT+01:00 Thomas Andraschko <
>> *andraschko.tho...@gmail.com* <andraschko.tho...@gmail.com>>:
>>
>>    Ok, seems like @PostConstruct of a @ManagedBean isn't called anymore.
>>
>>    Seems like the ManagedBean is instantiated correctly, the
>>    @ManagedProperty's are resolved but @PostConstruct isn't called.
>>    ManagedBeanBuilder ln213 calls the LifecycleProvider2 to do the
>>    @PostConstruct but nothing happens.
>>
>>    Any idea why a Tomcat7LifecycleProvider is used when running with
>>    mvn-jetty? As InstanceManager
>>    
>> *http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-api/8.0.12/org/apache/tomcat/SimpleInstanceManager.java*
>>    
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__grepcode.com_file_repo1.maven.org_maven2_org.apache.tomcat_tomcat-2Dapi_8.0.12_org_apache_tomcat_SimpleInstanceManager.java&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA&m=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y&s=shyuQdV3Hn5DYnmLRI4rxbWNyiVZYEhKlmYPTVPz3Ag&e=>
>>    is used, which really does nothing.
>>    Should this work? I wonder how did this ever work?
>>    Tried it again and faced the same problem with MF2.2 now....
>>
>>
>>    2018-02-26 23:09 GMT+01:00 Thomas Andraschko <
>>    *andraschko.tho...@gmail.com* <andraschko.tho...@gmail.com>>:
>>    Currently testing the PrimeFaces showcase and it seems something is
>>    broken regarding UIData :/
>>    Will come back after checking the details tomorrow. Our lazy
>>    datatable works fine with MF2.2 and Mojarra2.3 but not MF2.3.
>>
>>    2018-02-26 18:58 GMT+01:00 Eduardo B <*ebre...@gmail.com*
>>    <ebre...@gmail.com>>:
>>       Hello,
>>
>>       I was running the needed tasks to get the 2.3.0 release of Apache
>>       MyFaces core out.
>>
>>       Please note that this vote concerns the following part:
>>           1. Maven artifact group "org.apache.myfaces.core" v2.3.0  [1]
>>
>>       The artifacts were deployed on nexus repo [1] for binary and
>>       source packages.
>>
>>       The release notes could be found at [4].
>>
>>       Also the japicmp tool (similar to clirr tool) does not show binary
>>       incompatibilities with myfaces-api.
>>
>>       Please take a look at the "2.3.0" artifacts and vote! (see [3])
>>
>>       Please note: This vote is "majority approval" with a minimum of
>>       three +1 votes (see [2]).
>>
>>       ------------------------------------------------
>>       [ ] +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..............
>>       ------------------------------------------------
>>
>>       Thanks,
>>       Eduardo M. Breijo
>>
>>       [1]
>>       
>> *https://repository.apache.org/content/repositories/orgapachemyfaces-1130/org/apache/myfaces/core/*
>>       
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_orgapachemyfaces-2D1130_org_apache_myfaces_core_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA&m=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y&s=yQMoL-3J_esgYqgTyzIOLZx1EwEnF3rk_ovf525IzEY&e=>
>>       [2] *http://www.apache.org/foundation/voting.html#ReleaseVotes*
>>       
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_foundation_voting.html-23ReleaseVotes&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA&m=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y&s=T2DaUKjkArw2Jv9oUHG-Hza1g6604g3h3x-yzQj_6IE&e=>
>>       [3]
>>       
>> *https://repository.apache.org/content/repositories/orgapachemyfaces-1130/org/apache/myfaces/core/myfaces-core-assembly/*
>>       
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_orgapachemyfaces-2D1130_org_apache_myfaces_core_myfaces-2Dcore-2Dassembly_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA&m=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y&s=W231pmWnq5GfFjjPeJtWcCcIZZnQqUiIJ7yEKOG8Gfc&e=>
>>       [4]
>>       
>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12339569*
>>       
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_secure_ReleaseNote.jspa-3FprojectId-3D10600-26version-3D12339569&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA&m=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y&s=dF0Dw8SuO_-seG34zhe7n6OVl8syBCI32q8l14f9rso&e=>
>>
>>
>>
>>
>>
>>
>>
>

Reply via email to