Re: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Francois Armand

Steven Woolley wrote:

Can I petition that the closing tags not being rendered also be fixed before
5.1?  Not only did it cause invalid html, but also it actually affected the
rendering [...]


I seems quite important, but I believe it's not the good place for that 
: just open a bug and after, put the link to it here - the T5 dev could 
miss your post here, there is a lot of posts on this list.


Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17 won't 
be the GA). So I think it's quite possible that T5 dev includes a patch 
for that issue, if only they know how important it is.


Just my 2(€)cents ;)

--
Francois Armand
Etudes  Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
---
InterLDAP - http://interldap.org 
FederID - http://www.federid.org/

Open Source identities management and federation


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Steven Woolley


 I seems quite important, but I believe it's not the good place for that :
 just open a bug and after, put the link to it here - the T5 dev could miss
 your post here, there is a lot of posts on this list.


The bug had been closed and moved to the 5.1 branch.  I added my comment
there https://issues.apache.org/jira/browse/TAP5-333 but can't vote on it
now that it's closed, and don't think I can reopen it.



 Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17 won't be
 the GA). So I think it's quite possible that T5 dev includes a patch for
 that issue, if only they know how important it is.


Hence, the reason I posted here (hoping more users would chime in, it had 6
votes when closed).  5.0.18 please!!Steve


Re: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Howard Lewis Ship
https://issues.apache.org/jira/browse/TAP5-401

Wil be fixed shortly.  I'm deciding whether I should then generate
5.0.18 and put it to a vote.

On Thu, Dec 4, 2008 at 9:01 AM, Steven Woolley [EMAIL PROTECTED] wrote:


 I seems quite important, but I believe it's not the good place for that :
 just open a bug and after, put the link to it here - the T5 dev could miss
 your post here, there is a lot of posts on this list.


 The bug had been closed and moved to the 5.1 branch.  I added my comment
 there https://issues.apache.org/jira/browse/TAP5-333 but can't vote on it
 now that it's closed, and don't think I can reopen it.



 Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17 won't be
 the GA). So I think it's quite possible that T5 dev includes a patch for
 that issue, if only they know how important it is.


 Hence, the reason I posted here (hoping more users would chime in, it had 6
 votes when closed).  5.0.18 please!!Steve




-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Steven Woolley
woohoo!   Thanks!Steve

On Thu, Dec 4, 2008 at 11:12 AM, Howard Lewis Ship [EMAIL PROTECTED] wrote:

 https://issues.apache.org/jira/browse/TAP5-401

 Wil be fixed shortly.  I'm deciding whether I should then generate
 5.0.18 and put it to a vote.

 On Thu, Dec 4, 2008 at 9:01 AM, Steven Woolley [EMAIL PROTECTED] wrote:
 
 
  I seems quite important, but I believe it's not the good place for that
 :
  just open a bug and after, put the link to it here - the T5 dev could
 miss
  your post here, there is a lot of posts on this list.
 
 
  The bug had been closed and moved to the 5.1 branch.  I added my comment
  there https://issues.apache.org/jira/browse/TAP5-333 but can't vote on
 it
  now that it's closed, and don't think I can reopen it.
 
 
 
  Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17 won't
 be
  the GA). So I think it's quite possible that T5 dev includes a patch for
  that issue, if only they know how important it is.
 
 
  Hence, the reason I posted here (hoping more users would chime in, it had
 6
  votes when closed).  5.0.18 please!!Steve
 



 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




RE: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Blower, Andy
If you don't mind holding off a day, we'll be checking the fix for clustering 
ASO's tomorrow morning UK time. (today was just too full unfortunately)

 -Original Message-
 From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
 Sent: 04 December 2008 17:12
 To: Tapestry users
 Subject: Re: rendering unclosed tags - a petition to fix before 5.1

 https://issues.apache.org/jira/browse/TAP5-401

 Wil be fixed shortly.  I'm deciding whether I should then generate
 5.0.18 and put it to a vote.

 On Thu, Dec 4, 2008 at 9:01 AM, Steven Woolley [EMAIL PROTECTED]
 wrote:
 
 
  I seems quite important, but I believe it's not the good place for
 that :
  just open a bug and after, put the link to it here - the T5 dev
 could miss
  your post here, there is a lot of posts on this list.
 
 
  The bug had been closed and moved to the 5.1 branch.  I added my
 comment
  there https://issues.apache.org/jira/browse/TAP5-333 but can't vote
 on it
  now that it's closed, and don't think I can reopen it.
 
 
 
  Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17
 won't be
  the GA). So I think it's quite possible that T5 dev includes a patch
 for
  that issue, if only they know how important it is.
 
 
  Hence, the reason I posted here (hoping more users would chime in, it
 had 6
  votes when closed).  5.0.18 please!!Steve
 



 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: rendering unclosed tags - a petition to fix before 5.1

2008-12-04 Thread Howard Lewis Ship
Oops.  The vote went forward, but if there's a problem (there won't
be, I tested) we can always cancel the vote and generate a new 5.0.18.

On Thu, Dec 4, 2008 at 10:43 AM, Blower, Andy
[EMAIL PROTECTED] wrote:
 If you don't mind holding off a day, we'll be checking the fix for clustering 
 ASO's tomorrow morning UK time. (today was just too full unfortunately)

 -Original Message-
 From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
 Sent: 04 December 2008 17:12
 To: Tapestry users
 Subject: Re: rendering unclosed tags - a petition to fix before 5.1

 https://issues.apache.org/jira/browse/TAP5-401

 Wil be fixed shortly.  I'm deciding whether I should then generate
 5.0.18 and put it to a vote.

 On Thu, Dec 4, 2008 at 9:01 AM, Steven Woolley [EMAIL PROTECTED]
 wrote:
 
 
  I seems quite important, but I believe it's not the good place for
 that :
  just open a bug and after, put the link to it here - the T5 dev
 could miss
  your post here, there is a lot of posts on this list.
 
 
  The bug had been closed and moved to the 5.1 branch.  I added my
 comment
  there https://issues.apache.org/jira/browse/TAP5-333 but can't vote
 on it
  now that it's closed, and don't think I can reopen it.
 
 
 
  Moreover, it seems that a 5.0.18 will come (and so that the 5.0.17
 won't be
  the GA). So I think it's quite possible that T5 dev includes a patch
 for
  that issue, if only they know how important it is.
 
 
  Hence, the reason I posted here (hoping more users would chime in, it
 had 6
  votes when closed).  5.0.18 please!!Steve
 



 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]