[jira] [Commented] (TOBAGO-1736) Incorrectly rendered component ID

2017-05-01 Thread Leonardo Uribe (JIRA)

[ 
https://issues.apache.org/jira/browse/TOBAGO-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992005#comment-15992005
 ] 

Leonardo Uribe commented on TOBAGO-1736:


c:forEach has been a pain for a long time, and the changes involved to fix this 
has been included slowly in MyFaces Core 2.1/2.2 versions. 

The fundamental problem is c:forEach is a build view time tag, that alters the 
component tree structure, but the old algorithm from facelets lacks of the 
necessary logic to do it properly. It is a long story, see MYFACES-3811 for 
details.

I agree with Volker, it is not a Tobago issue.

> Incorrectly rendered component ID
> -
>
> Key: TOBAGO-1736
> URL: https://issues.apache.org/jira/browse/TOBAGO-1736
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Facelets
>Affects Versions: 2.0.10
> Environment: Unix
>Reporter: David Crhonek
> Attachments: uploadBox.xhtml
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> When dynamically creating UI component ID, the rendered ID is often 
> incorrect. This appears to be random, but happens very often, multiple times 
> on a page. When the same value is put in ID and in tip (title), the rendered 
> title is ALWAYS correct, however the rendered ID value is often INCORRECT.
> In the attached example, #{titleVar} is put to ID as well as to tip. This is 
> an example of an incorrect output:
>  id="page:details_upload:CASV3_C_B_TODAY" title="NTC_A_B_TODAY" 
> data-tobago-commands="{click:{partially:page:details_upload:popup-Upload-TODAY-1,popup:{command:open}}}"
>  href="#" 
> data-tobago-style="{width:59px,height:14px,top:52px,left:677px,position:absolute}"
>  class="tobago-button" style="width: 59px; height: 14px; top: 52px; left: 
> 677px; position: absolute;">Upload
> ID and Title should be the same, but they are not. The expected value is 
> NTC_A_B_TODAY



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


Re: [VOTE] Release of MyFaces Trinidad 2.2.0

2017-05-01 Thread Leonardo Uribe
+1

2017-05-01 13:47 GMT-05:00 Dennis Kieselhorst :

> +1
>
> Just noticed that trinidad-assembly contains duplicated artifacts and
> opened an issue for it: https://issues.apache.org/
> jira/browse/TRINIDAD-2554
>


Re: [VOTE] Release of MyFaces Trinidad 2.1.3

2017-05-01 Thread Leonardo Uribe
+1

2017-05-01 13:39 GMT-05:00 Dennis Kieselhorst :

> +1
>


Re: [VOTE] Release of MyFaces Trinidad 2.2.0

2017-05-01 Thread Dennis Kieselhorst
+1

Just noticed that trinidad-assembly contains duplicated artifacts and
opened an issue for it: https://issues.apache.org/jira/browse/TRINIDAD-2554


[jira] [Created] (TRINIDAD-2554) Avoid duplicated trinidad-assembly artifacts

2017-05-01 Thread Dennis Kieselhorst (JIRA)
Dennis Kieselhorst created TRINIDAD-2554:


 Summary: Avoid duplicated trinidad-assembly artifacts
 Key: TRINIDAD-2554
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2554
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Build
Affects Versions: 2.2.0-core
Reporter: Dennis Kieselhorst
Priority: Minor


trinidad-assembly contains duplicated artifacts (with and without -dist). No 
need to upload them twice. According to download page -dist is expected.



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


Re: [VOTE] Release of MyFaces Trinidad 2.1.3

2017-05-01 Thread Dennis Kieselhorst
+1


Re: [VOTE] Release of MyFaces Trinidad 2.2.0

2017-05-01 Thread Udo Schnurpfeil
+1

Regards,

Udo

Am 28.04.17 um 21:39 schrieb Bernd Bohmann:
> Hello
> 
> I was running the needed tasks to get the 2.2.0 release of Apache
> MyFaces Trinidad out.
> 
> Please note that this vote concerns the following parts:
> 1. Maven artifact group "org.apache.myfaces.trinidad" v2.2.0
> 
> The artifacts were deployed on nexus repo
> 
> https://repository.apache.org/content/repositories/orgapachemyfaces-1106/
> 
> with binary and source packages.
> 
> The release notes could be found at:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661=12340363
> 
> Please take a look at the "2.2.0" artifacts and vote!
> 
> Please note: This vote is "majority approval" with a minimum of three
> +1 votes (see [1]).
> 
> ---
> [ ] +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
> 
> Bernd
> 
> [1] http://www.apache.org/foundation/voting.html#ReleaseVotes
> 


Re: [VOTE] Release of MyFaces Trinidad 2.1.3

2017-05-01 Thread Udo Schnurpfeil
+1

Regards,

Udo

Am 28.04.17 um 21:37 schrieb Bernd Bohmann:
> Hello
> 
> I was running the needed tasks to get the 2.1.3 release of Apache
> MyFaces Trinidad out.
> 
> Please note that this vote concerns the following parts:
> 1. Maven artifact group "org.apache.myfaces.trinidad" v2.1.3
> 
> The artifacts were deployed on nexus repo 
> 
> https://repository.apache.org/content/repositories/orgapachemyfaces-1105/
> 
> with binary and source packages.
> 
> The release notes could be found at:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661=12339845
> 
> Please take a look at the "2.1.3" artifacts and vote!
> 
> Please note: This vote is "majority approval" with a minimum of three
> +1 votes (see [1]).
> 
> ---
> [ ] +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
> 
> Bernd
> 
> [1] http://www.apache.org/foundation/voting.html#ReleaseVotes
>