Re: [VOTE] release of MyFaces Core 2.3.0

[Eduardo B]

Thanks everybody for voting.

We have more than three +1 votes so I will finish up the release of MyFaces
Core 2.3.0 this week.

Regards,
Eduardo M. Breijo

On Sat, Mar 3, 2018 at 7:52 AM, Dennis Kieselhorst  wrote:

> +1
>
> Cheers
> Dennis
>

Re: [VOTE] release of MyFaces Core 2.3.0

[Dennis Kieselhorst]

+1

Cheers
Dennis

Re: [VOTE] release of MyFaces Core 2.3.0

[Bill Lucy]

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=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=shyuQdV3Hn5DYnmLRI4rxbWNyiVZYEhKlmYPTVPz3Ag=>
>>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_repositorie

Re: [VOTE] release of MyFaces Core 2.3.0

[Eduardo B]

+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=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=shyuQdV3Hn5DYnmLRI4rxbWNyiVZYEhKlmYPTVPz3Ag=>
>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_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=yQMoL-3J_esgYqgTyzIOLZx1EwEnF3rk_ovf525IzEY=>
>   [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=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=T2DaUKjkArw2Jv9oUHG-Hza1g6604g3h3x-yzQj_6IE=>
>   [3]
&

Re: [VOTE] release of MyFaces Core 2.3.0

[Udo Schnurpfeil]

+1

Regards,

Udo


Am 27.02.18 um 16:22 schrieb Paul Nicolucci:
>
> +1
>
> Thanks,
>
> Paul Nicolucci
>
>
> Inactive hide details for Thomas Andraschko ---02/26/2018 06:04:03
> PM---Ok, but as ManagedBeans are deprecated, it also fails wThomas
> 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>
> To: MyFaces Development <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.thomas@gmail.com_ <mailto: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=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=shyuQdV3Hn5DYnmLRI4rxbWNyiVZYEhKlmYPTVPz3Ag=>
> 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.thomas@gmail.com_ <mailto: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 <_ebreijo@gmail.com_
> <mailto: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_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=yQMoL-3J_esgYqgTyzIOLZx1EwEnF3rk_ovf525IzEY=>
> [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=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=n-2RUhyQkncKQNTGKy9UmSKIHKSZzEVYEqiy1H7hEwA=GQI8rpQoDrdQHm_Galm9hft6-jzEr-7wUHBq_Y-ah_Y=T2DaUKjkArw2Jv9oUHG-Hza1g6604g3h3x-yzQj_6IE=>
> [3]
> 
> _https://repository.ap

Re: [VOTE] release of MyFaces Core 2.3.0

[Dennis Kieselhorst]

Hi Eduardo,

thanks for building the release. I plan to check it on the weekend. Sorry for 
the delay...

Cheers
Dennis

Re: [VOTE] release of MyFaces Core 2.3.0

[Paul Nicolucci]

+1

Thanks,

Paul Nicolucci




From:   Thomas Andraschko <andraschko.tho...@gmail.com>
To: MyFaces Development <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>:
  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
   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
  >:
   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>:
 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/
 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
 [3]
 
https://repository.apache.org/content/repositories/orgapachemyfaces-1130/org/apache/myfaces/core/myfaces-core-assembly/
 [4]
 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12339569

Re: [VOTE] release of MyFaces Core 2.3.0

[Thomas Andraschko]

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 :

> 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 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 
> :
>
>> 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 :
>>
>>> 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/orgapache
>>> myfaces-1130/org/apache/myfaces/core/
>>> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
>>> [3] https://repository.apache.org/content/repositories/orgapache
>>> myfaces-1130/org/apache/myfaces/core/myfaces-core-assembly/
>>> [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=10600=12339569
>>>
>>
>>
>

Re: [VOTE] release of MyFaces Core 2.3.0

[Thomas Andraschko]

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
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 :

> 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 :
>
>> 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/orgapache
>> myfaces-1130/org/apache/myfaces/core/
>> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
>> [3] https://repository.apache.org/content/repositories/orgapache
>> myfaces-1130/org/apache/myfaces/core/myfaces-core-assembly/
>> [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=10600=12339569
>>
>
>

Re: [VOTE] release of MyFaces Core 2.3.0

[Thomas Andraschko]

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 :

> 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/
> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
> [3] https://repository.apache.org/content/repositories/
> orgapachemyfaces-1130/org/apache/myfaces/core/myfaces-core-assembly/
> [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=10600=12339569
>

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Udo Schnurpfeil]

+1

Regard, Udo

Am 09.06.17 um 03:30 schrieb Leonardo Uribe:
> Hi,
> 
> I was running the needed tasks to get the 2.3.0-beta release of Apache
> MyFaces core out.
> 
> 
> Please note that this vote concerns all of the following parts:
>  1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta  [1]
> 
> The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
> 
> 
> Thanks,
> Leonardo Uribe
> 
> [1]
> https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/
> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
> [3]
> https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/
> [4]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Dennis Kieselhorst]

> We need an extra +1 from a PMC member in order to continue with the beta
> release. Someone who likes to review the bits?

I'll definitely take a look after my holidays next week.

Regards
Dennis

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Thomas Andraschko]

+1

2017-06-14 4:32 GMT+02:00 Leonardo Uribe <lu4...@gmail.com>:

> Hi
>
> We need an extra +1 from a PMC member in order to continue with the beta
> release. Someone who likes to review the bits?
>
> regards,
>
> Leonardo Uribe
>
> 2017-06-10 6:15 GMT-05:00 Paul Nicolucci <pnico...@us.ibm.com>:
>
>> +1
>>
>> Regards,
>>
>> Paul Nicolucci
>>
>>
>> [image: Inactive hide details for Bill Lucy ---06/09/2017 11:25:45
>> AM---+1 - the progress looks great! Bill]Bill Lucy ---06/09/2017
>> 11:25:45 AM---+1 - the progress looks great! Bill
>>
>> From: Bill Lucy <wtl...@gmail.com>
>> To: MyFaces Development <dev@myfaces.apache.org>
>> Date: 06/09/2017 11:25 AM
>> Subject: Re: [VOTE] release of MyFaces Core 2.3.0-beta
>> --
>>
>>
>>
>> +1 - the progress looks great!
>>
>> Bill
>>
>> On Fri, Jun 9, 2017 at 1:41 AM, Mustafa Agâh Öztürk <*maozt...@msn.com*
>> <maozt...@msn.com>> wrote:
>>
>>+1 from me.
>>
>>
>>On 06/09/2017 04:30 AM, Leonardo Uribe wrote:
>>+1
>>
>>  2017-06-08 20:30 GMT-05:00 Leonardo Uribe <*lu4...@gmail.com*
>>  <lu4...@gmail.com>>:
>>  Hi,
>>
>>  I was running the needed tasks to get the 2.3.0-beta release of
>>  Apache
>>  MyFaces core out.
>>
>>
>>  Please note that this vote concerns all of the following parts:
>>   1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta
>>  [1]
>>
>>  The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
>>  
>>
>>  Thanks,
>>  Leonardo Uribe
>>
>>  [1]
>>  
>> *https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/*
>>  
>> <https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/>
>>  [2] *http://www.apache.org/foundation/voting.html#ReleaseVotes*
>>  <http://www.apache.org/foundation/voting.html#ReleaseVotes>
>>  [3]
>>  
>> *https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/*
>>  
>> <https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/>
>>  [4]
>>  
>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857*
>>  
>> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857>
>>
>>
>>
>>
>>
>>
>

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Leonardo Uribe]

Hi

We need an extra +1 from a PMC member in order to continue with the beta
release. Someone who likes to review the bits?

regards,

Leonardo Uribe

2017-06-10 6:15 GMT-05:00 Paul Nicolucci <pnico...@us.ibm.com>:

> +1
>
> Regards,
>
> Paul Nicolucci
>
>
> [image: Inactive hide details for Bill Lucy ---06/09/2017 11:25:45 AM---+1
> - the progress looks great! Bill]Bill Lucy ---06/09/2017 11:25:45 AM---+1
> - the progress looks great! Bill
>
> From: Bill Lucy <wtl...@gmail.com>
> To: MyFaces Development <dev@myfaces.apache.org>
> Date: 06/09/2017 11:25 AM
> Subject: Re: [VOTE] release of MyFaces Core 2.3.0-beta
> --
>
>
>
> +1 - the progress looks great!
>
> Bill
>
> On Fri, Jun 9, 2017 at 1:41 AM, Mustafa Agâh Öztürk <*maozt...@msn.com*
> <maozt...@msn.com>> wrote:
>
>+1 from me.
>
>
>On 06/09/2017 04:30 AM, Leonardo Uribe wrote:
>+1
>
>  2017-06-08 20:30 GMT-05:00 Leonardo Uribe <*lu4...@gmail.com*
>  <lu4...@gmail.com>>:
>  Hi,
>
>  I was running the needed tasks to get the 2.3.0-beta release of
>  Apache
>  MyFaces core out.
>
>
>  Please note that this vote concerns all of the following parts:
>   1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta
>  [1]
>
>  The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
>  
>
>  Thanks,
>  Leonardo Uribe
>
>  [1]
>  
> *https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/*
>  
> <https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/>
>  [2] *http://www.apache.org/foundation/voting.html#ReleaseVotes*
>  <http://www.apache.org/foundation/voting.html#ReleaseVotes>
>  [3]
>  
> *https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/*
>  
> <https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/>
>  [4]
>  
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857*
>  
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857>
>
>
>
>
>
>

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Paul Nicolucci]

+1

Regards,

Paul Nicolucci




From:   Bill Lucy <wtl...@gmail.com>
To: MyFaces Development <dev@myfaces.apache.org>
Date:   06/09/2017 11:25 AM
Subject:    Re: [VOTE] release of MyFaces Core 2.3.0-beta



+1 - the progress looks great!

Bill

On Fri, Jun 9, 2017 at 1:41 AM, Mustafa Agâh Öztürk <maozt...@msn.com>
wrote:
  +1 from me.



  On 06/09/2017 04:30 AM, Leonardo Uribe wrote:
+1

2017-06-08 20:30 GMT-05:00 Leonardo Uribe <lu4...@gmail.com>:
 Hi,

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


 Please note that this vote concerns all of the following parts:
  1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta
 [1]

 The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
 

 Thanks,
 Leonardo Uribe

 [1]
 
https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/

 [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
 [3]
 
https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/

 [4]
 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Bill Lucy]

+1 - the progress looks great!

Bill

On Fri, Jun 9, 2017 at 1:41 AM, Mustafa Agâh Öztürk 
wrote:

> +1 from me.
>
> On 06/09/2017 04:30 AM, Leonardo Uribe wrote:
>
> +1
>
> 2017-06-08 20:30 GMT-05:00 Leonardo Uribe :
>
>> Hi,
>>
>> I was running the needed tasks to get the 2.3.0-beta release of Apache
>> MyFaces core out.
>>
>>
>> Please note that this vote concerns all of the following parts:
>>  1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta  [1]
>>
>> The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
>> 
>>
>> Thanks,
>> Leonardo Uribe
>>
>> [1] https://repository.apache.org/content/repositories/orgapache
>> myfaces-1109/org/apache/myfaces/
>> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
>> [3] https://repository.apache.org/content/repositories/orgapache
>> myfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/
>> [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=10600=12340857
>>
>
>
>

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Mustafa Agâh Öztürk]

+1 from me.

On 06/09/2017 04:30 AM, Leonardo Uribe wrote:
+1

2017-06-08 20:30 GMT-05:00 Leonardo Uribe 
>:
Hi,

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


Please note that this vote concerns all of the following parts:
 1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta  [1]

The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..


Thanks,
Leonardo Uribe

[1] 
https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/
[2] http://www.apache.org/foundation/voting.html#ReleaseVotes
[3] 
https://repository.apache.org/content/repositories/orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/
[4] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12340857

Re: [VOTE] release of MyFaces Core 2.3.0-beta

[Leonardo Uribe]

+1

2017-06-08 20:30 GMT-05:00 Leonardo Uribe :

> Hi,
>
> I was running the needed tasks to get the 2.3.0-beta release of Apache
> MyFaces core out.
>
>
> Please note that this vote concerns all of the following parts:
>  1. Maven artifact group "org.apache.myfaces.core" v2.3.0-beta  [1]
>
> The artifacts were deployed on nexus repo [1] 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.3.0-beta" 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..
> 
>
> Thanks,
> Leonardo Uribe
>
> [1] https://repository.apache.org/content/repositories/
> orgapachemyfaces-1109/org/apache/myfaces/
> [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
> [3] https://repository.apache.org/content/repositories/
> orgapachemyfaces-1109/org/apache/myfaces/core/myfaces-core-assembly/
> [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=10600=12340857
>