Re: [VOTE] release of MyFaces Core 2.3.3

2019-01-29 Thread Matthew Broadhead

+1

On 29/01/2019 15:58, Udo Schnurpfeil wrote:


+1

Am 29.01.19 um 15:36 schrieb Bill Lucy:

+1

On Mon, Jan 28, 2019 at 3:34 PM Eduardo Breijo > wrote:


+1

Thanks!
Eduardo

On Mon, Jan 28, 2019 at 2:16 PM Paul Nicolucci
mailto:pnico...@us.ibm.com>> wrote:

My +1

Regards,

Paul Nicolucci

Inactive hide details for Thomas Andraschko ---01/28/2019
02:13:55 PM---+1 thanks paul!Thomas Andraschko ---01/28/2019
02:13:55 PM---+1 thanks paul!

From: Thomas Andraschko mailto:andraschko.tho...@gmail.com>>
To: MyFaces Development mailto:dev@myfaces.apache.org>>
Date: 01/28/2019 02:13 PM
Subject: Re: [VOTE] release of MyFaces Core 2.3.3





+1
thanks paul!

Am Mo., 28. Jan. 2019 um 17:24 Uhr schrieb Paul Nicolucci
<_pnico...@us.ibm.com_ >:

Hi,

I was running the needed tasks to get the 2.3.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.core"
v2.3.3  [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) shows the only
api changes from 2.3.2 to 2.3.3 are the expected changes
from
_https://issues.apache.org/jira/browse/MYFACES-4251_.
I've attached the results to this email as well
(results.html).
/
(See attached file: results.html)/

Please take a look at the "2.3.3" 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,
Paul Nicolucci

[1]

_https://repository.apache.org/content/repositories/orgapachemyfaces-1147/org/apache/myfaces/core/_
[2]
_http://www.apache.org/foundation/voting.html#ReleaseVotes_
[3]

_https://repository.apache.org/content/repositories/orgapachemyfaces-1147/org/apache/myfaces/core/myfaces-core-assembly/_
[4]

_https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12344007_




--
Mr MT Broadhead
Nigel Broadhead Mynard
See the latest jobs available at NBM @ https://nbmlaw.co.uk/recruitment.htm

32 Rainsford Road
Chelmsford Essex CM1 2QG
Tel: 01245 269909 Fax: 01245 261932
https://nbmlaw.co.uk

Partners: WJ Broadhead NP Eason SJ Lacey CR Broadhead D Seepaul T Carley

Nigel Broadhead Mynard Solicitors are authorised and regulated by the 
Solicitors Regulation Authority. We are also bound by their code of conduct. 
Registered no. 00061052

Nigel Broadhead Mynard also provide a will writing service, see 
https://nbmlaw.co.uk/wills.htm for more information

Confidentiality: Information in this message is confidential and may be legally 
privileged. It is intended solely for the recipient to whom it is addressed. If 
you receive the message in error, please notify the sender and immediately 
destroy all copies.

Security warning: Please note that this e-mail has been created in the 
knowledge that e-mail is not a 100% secure communications medium. We advise you 
that you understand and observe this lack of security when e-mailing us. This 
e-mail does not constitute a legally binding document. No contracts may be 
concluded on behalf of Nigel Broadhead Mynard Solicitors by e-mail 
communications.

Disclaimer: Please be aware of cyber crime. Nigel Broadhead Mynard will not 
take responsibility if you transfer money to a wrong bank account. Please speak 
to your Solicitor before transferring any money. If you receive an email from 
Nigel Broadhead Mynard requesting your bank details or telling you our bank 
details have changed, please contact your Solicitor immediately to clarify.

PLEASE ALSO NOTE that Nigel Broadhead Mynard only use emails which end with the suffix 
@nbmlaw.co.uk.  If you receive any email from an address without that suffix or where 
that suffix does not appear in the address box when you click "Reply" then you 
should not rely on the email being from NBM and you should immediately contact us on the 
above number or any numbers published on our website to verify the source of the email is 
genuine.

Re: [VOTE] Release Tobago 2.3.0

2018-10-31 Thread Matthew Broadhead

+1

On 31/10/2018 15:44, Dennis Kieselhorst wrote:

+1




Re: MyFaces 3.x - Remove "Impl Shaded" + "Impl Shaded Public"? @cc tobago-guys :P

2018-10-18 Thread Matthew Broadhead

+1
from the tidying up point of view but it depends what the tobago guys think

On 18/10/2018 13:54, Thomas Andraschko wrote:

Hi,

MyFaces Core Impl Shaded + Shaded Public was used years ago in other 
component libaries like Trinidad, Tobago and Tomhawk, right?


Currently neither Trinidad nor Tomhawk is still active - and Tobago 
doesn't use it, right?


As i said already said, 3.x is a good time to cleanup the project, as 
some legacy parts of JSF like ManagedBeans and Faces EL will be removed.


I think it would be the right time to also merge back the "Shared 
Impls" into the "Impl" module and remove some unused stuff.


I really would see it as an chance now, to make MyFaces maintainable 
for the next years and cleanup as much as possible!


Mojarra takes the chance and even moved away from their old ant-based 
builds! :D


WDYT?
I would do all the work. We have over 1000 unittests, so i don't think 
we will break something ;)


Best regards,
Thomas





Re: MyFaces Core 3.0

2018-10-10 Thread Matthew Broadhead
sounds like a great idea.  it may result in performance gain or at least 
making the newer code less cluttered.  what replaces Faces EL?


On 10/10/18 16:29, Thomas Andraschko wrote:

Hi all,

i would like to start a discussion about MyFaces 3.0.

Mojarra started with removing old code for Mojarra 3.0 like removing 
the "long time deprecated" managed beans and faces EL.


I probably have some free time during the cold months, so i would like 
to start with those changes. Maybe already this month.


The first steps are:
- move master to 2.3.x branch
- make master 3.0.x
- remove managed beans
- remove facelets EL

As managed beans are removed and JSF goes "full CDI", does it make 
sense to still support our internal SPI like InjectionProvider? I 
don't think so.


I think it's a good chance to cleanup the project in generell -  AFAIR 
3.0 also removes support of JSPs.

We can of course discuss each part to cleanup later in a own thread.

WDYT?

Regards,
Thomas









Re: [VOTE] Release Tobago 2.2.0, 3.1.0, 4.3.0 and checkstyle-rules 11

2018-09-23 Thread Matthew Broadhead

+1 (non binding)
demo looks good

On 23/09/18 20:48, Udo Schnurpfeil wrote:

Hello,

We would like to release
* Tobago 4.3.0
* Tobago 3.1.0
* Tobago 2.2.0
* checkstyle-rules 11

The demos on http://tobago-vm.apache.org/ where updated.

Major changes since last release are:

Tobago 4.3.0
* New toggle component: 
* Update to Bootstrap 4.1.3
* Update to jQuery 3
* Vertical align vor Sheets
* "plain" attribute
* "keepLineBreaks" attribute
* Icons in FacesMessages
* tooltip for 
* java.util.Calendar and java.time.DateTime support for 
* LabelLayout attributes gridLeft, gridRight
* Passwords aren't sent to the client
* Bugfixes

Tobago 3.1.0
* Update to jQuery 3
* Passwords aren't sent to the client
* Bugfixes

Tobago 2.2.0
* Update to jQuery 3 (IE 8 is no longer supported!)
* PageState is usable for layout
* Passwords aren't sent to the client
* Bugfixes

checkstyle-rules 11
* update rules for dependency-check

For a detail list please consult the release notes at:

Tobago 4.3.0
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=

Tobago 3.1.0
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=

Tobago 2.2.0
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=


The version is available at the staging repository (Nexus) at:

Tobago 4.3.0
https://repository.apache.org/content/repositories/orgapachemyfaces-1141/
The sources are (sha-256
1820770135e5a6ac6a17c80daf152e7e4caf97c6511a1c94be52178611471ac6):
https://repository.apache.org/content/repositories/orgapachemyfaces-1141/org/apache/myfaces/tobago/tobago/4.3.0/tobago-4.3.0-source-release.zip

Tobago 3.1.0
https://repository.apache.org/content/repositories/orgapachemyfaces-1140/
The sources are (sha-256
d9fdfc949afef61de8ced16906864f6ace7708364212a55a3ae644f2b67ff3a6):
https://repository.apache.org/content/repositories/orgapachemyfaces-1140/org/apache/myfaces/tobago/tobago/3.1.0/tobago-3.1.0-source-release.zip

Tobago 2.2.0
https://repository.apache.org/content/repositories/orgapachemyfaces-1139/
The sources are (sha-256
82ff4b3cec7e45537083ee9e6c1da90da964e40323230156e16156f55062ae7d):
https://repository.apache.org/content/repositories/orgapachemyfaces-1139/org/apache/myfaces/tobago/tobago/2.2.0/tobago-2.2.0-source-release.zip

checkstyle-rules 11
https://repository.apache.org/content/repositories/orgapachemyfaces-1142/
The sources are (sha-256
e70bd321c024d96d240ddadab4b6e73c1c0e2c89067a20abc3388f71a9e7b368):
https://repository.apache.org/content/repositories/orgapachemyfaces-1142/org/apache/myfaces/buildtools/checkstyle-rules/11/checkstyle-rules-11-source-release.zip


Please vote now! (The vote is open for 72h.)

[ ] +1
[ ] +0
[ ] -1

Regards,

Udo





[jira] [Commented] (MYFACES-4081) h inputFile size limit

2017-02-05 Thread Matthew Broadhead (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853252#comment-15853252
 ] 

Matthew Broadhead commented on MYFACES-4081:


if anyone else has the problem it was a configuration issue in server.xml in 
the connector maxPostSize
{code:xml}{code}
sets it to unlimited but you might want a more sensible value.  what is 
annoying was that there was no error or feedback reported it just drops the 
connextion.

> h inputFile size limit
> --
>
> Key: MYFACES-4081
> URL: https://issues.apache.org/jira/browse/MYFACES-4081
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.3
> Environment: TomEE 7.0.2
>    Reporter: Matthew Broadhead
>
> h inputFile seems to be limited to a file size of around 1MB.  no error is 
> thrown if file exceeds this size.  javascript console shows 
> net::ERR_CONNECTION_RESET
> i have tried changing these settings 
> {code:xml}
> 
>   Faces Servlet
>   javax.faces.webapp.FacesServlet
>   1
>   
>   20848820
>   418018841
>   1048576
>   
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MYFACES-4081) h inputFile size limit

2017-01-19 Thread Matthew Broadhead (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831360#comment-15831360
 ] 

Matthew Broadhead commented on MYFACES-4081:


sorry to double post but wan't that fix also applied to 2.2.2?

> h inputFile size limit
> --
>
> Key: MYFACES-4081
> URL: https://issues.apache.org/jira/browse/MYFACES-4081
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.3
> Environment: TomEE 7.0.2
>Reporter: Matthew Broadhead
>
> h inputFile seems to be limited to a file size of around 1MB.  no error is 
> thrown if file exceeds this size.  javascript console shows 
> net::ERR_CONNECTION_RESET
> i have tried changing these settings 
> {code:xml}
> 
>   Faces Servlet
>   javax.faces.webapp.FacesServlet
>   1
>   
>   20848820
>   418018841
>   1048576
>   
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MYFACES-4081) h inputFile size limit

2017-01-19 Thread Matthew Broadhead (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831356#comment-15831356
 ] 

Matthew Broadhead commented on MYFACES-4081:


i am kind of stuck with what comes with TomEE 7.0.2 but I will ask Romain the 
best option

> h inputFile size limit
> --
>
> Key: MYFACES-4081
> URL: https://issues.apache.org/jira/browse/MYFACES-4081
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.3
> Environment: TomEE 7.0.2
>    Reporter: Matthew Broadhead
>
> h inputFile seems to be limited to a file size of around 1MB.  no error is 
> thrown if file exceeds this size.  javascript console shows 
> net::ERR_CONNECTION_RESET
> i have tried changing these settings 
> {code:xml}
> 
>   Faces Servlet
>   javax.faces.webapp.FacesServlet
>   1
>   
>   20848820
>   418018841
>   1048576
>   
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (MYFACES-4081) h inputFile size limit

2017-01-19 Thread Matthew Broadhead (JIRA)
Matthew Broadhead created MYFACES-4081:
--

 Summary: h inputFile size limit
 Key: MYFACES-4081
 URL: https://issues.apache.org/jira/browse/MYFACES-4081
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.2.3
 Environment: TomEE 7.0.2
Reporter: Matthew Broadhead


h inputFile seems to be limited to a file size of around 1MB.  no error is 
thrown if file exceeds this size.  javascript console shows 
net::ERR_CONNECTION_RESET

i have tried changing these settings 
{code:xml}

Faces Servlet
javax.faces.webapp.FacesServlet
1

20848820
418018841
1048576


{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (MYFACES-4073) h:inputFile required attribute ignored

2016-10-29 Thread Matthew Broadhead (JIRA)
Matthew Broadhead created MYFACES-4073:
--

 Summary: h:inputFile required attribute ignored
 Key: MYFACES-4073
 URL: https://issues.apache.org/jira/browse/MYFACES-4073
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.2.3
 Environment: TomEE 7.0.1
Reporter: Matthew Broadhead


xmlns:h="http://xmlns.jcp.org/jsf/html";  generally seems to work 
fine for uploading a file.  However the required attribute does not seem to be 
respected.  Setting it to true still allows the form to be submitted where no 
file has been selected for upload



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MYFACES-4072) passthrough checked always set

2016-10-27 Thread Matthew Broadhead (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611667#comment-15611667
 ] 

Matthew Broadhead commented on MYFACES-4072:


According to the article any value other than null should result in checked. 
Otherwise omit attribute completely. Not sure what the spec says

> passthrough checked always set
> --
>
> Key: MYFACES-4072
> URL: https://issues.apache.org/jira/browse/MYFACES-4072
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.3
> Environment: TomEE 7.0.1
>    Reporter: Matthew Broadhead
>
> following the tutorial outlined in this BalusC article 
> http://balusc.omnifaces.org/2015/10/custom-layout-with-hselectoneradio-in.html
>  it seems that when a:checked 
> (xmlns:a="http://xmlns.jcp.org/jsf/passthrough";) is set to null it still 
> renders as checked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (MYFACES-4072) passthrough checked always set

2016-10-25 Thread Matthew Broadhead (JIRA)
Matthew Broadhead created MYFACES-4072:
--

 Summary: passthrough checked always set
 Key: MYFACES-4072
 URL: https://issues.apache.org/jira/browse/MYFACES-4072
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.2.3
 Environment: TomEE 7.0.1
Reporter: Matthew Broadhead


following the tutorial outlined in this BalusC article 
http://balusc.omnifaces.org/2015/10/custom-layout-with-hselectoneradio-in.html 
it seems that when a:checked (xmlns:a="http://xmlns.jcp.org/jsf/passthrough";) 
is set to null it still renders as checked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)