[
https://issues.apache.org/jira/browse/TRINIDAD-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1193:
-
Resolution: Fixed
Fix Version/s: 1.0.10-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625993#action_12625993
]
Matthias Weßendorf commented on TRINIDAD-1195:
--
Tested this (in JSPX):
On Tue, Aug 26, 2008 at 4:50 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Option 3?
Add links to the URLs to produce the JIRA release notes
what do you mean ?
add a form to load the release notes for release 1.x.y ?
On Tue, Aug 26, 2008 at 1:45 AM, Matthias Wessendorf [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626100#action_12626100
]
Stephen Friedrich commented on TRINIDAD-1195:
-
No, this is not a seam issue.
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1195.
--
Resolution: Fixed
Fix Version/s: 1.0.10-core
Jira operates by query string doesn't it? If so, each release, a link
could be added to the
http://myfaces.apache.org/trinidad/release-notes.html page that simply
opens the Jira report by that query string. For example, here is the
1.2.9 release link:
On Wed, Aug 27, 2008 at 6:09 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Jira operates by query string doesn't it? If so, each release, a link
could be added to the
http://myfaces.apache.org/trinidad/release-notes.html page that simply
opens the Jira report by that query string. For example,
Hi,
I was running the needed tasks to get the 1.2.4 release of Apache
MyFaces core out.
The artifacts passed all TCK test.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v3.0.4 [1]
2. Maven artifact group
+0 sorry I'm swamped. Good job on the TCK.
On 8/27/08, Hazem Saleh [EMAIL PROTECTED] wrote:
+1, Thanks Leonardo.
On Wed, Aug 27, 2008 at 9:08 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Wed, Aug 27, 2008 at 1:07 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the
+1
2008/8/27 Grant Smith [EMAIL PROTECTED]
+0 sorry I'm swamped. Good job on the TCK.
On 8/27/08, Hazem Saleh [EMAIL PROTECTED] wrote:
+1, Thanks Leonardo.
On Wed, Aug 27, 2008 at 9:08 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Wed, Aug 27, 2008 at 1:07 PM, Leonardo Uribe [EMAIL
+1
On Wed, Aug 27, 2008 at 9:43 PM, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
2008/8/27 Grant Smith [EMAIL PROTECTED]
+0 sorry I'm swamped. Good job on the TCK.
On 8/27/08, Hazem Saleh [EMAIL PROTECTED] wrote:
+1, Thanks Leonardo.
On Wed, Aug 27, 2008 at 9:08 PM, Leonardo Uribe [EMAIL
On Wed, Aug 27, 2008 at 1:53 PM, Cagatay Civici [EMAIL PROTECTED]wrote:
Hi,
I'm planning to move SecurityContext EL feature out of the sandbox. It's EL
extensions for security.
What should it's new location be? myfaces-commons(what's the situtation of
commons btw) or tomahawk?
Firefox warns about Error in parsing value for property 'cursor'. Declaration
dropped.
---
Key: TOMAHAWK-1320
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1320
[
https://issues.apache.org/jira/browse/TRINIDAD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626305#action_12626305
]
Simon Lessard commented on TRINIDAD-205:
It's true that an interface would be
[
https://issues.apache.org/jira/browse/TRINIDAD-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ari hadi updated TRINIDAD-1191:
---
Status: Open (was: Patch Available)
Delayed loading of renderers to facilitate faster start up
It is acceptable to me. Perhaps you can create a JIRA for these kinds of
cleanups (and/or add a TODO to the code). This Skinning code has been
around and added to for many years, and could use a cleanup. I
definitely agree with the StyleContext and StyleProvider being linked.
That is really
Implement JSF 2.0 Early Draf 2008-04-21
---
Key: MYFACES-1909
URL: https://issues.apache.org/jira/browse/MYFACES-1909
Project: MyFaces Core
Issue Type: Task
Reporter: Simon Lessard
[
https://issues.apache.org/jira/browse/TOMAHAWK-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated TOMAHAWK-1297:
-
Resolution: Fixed
Fix Version/s: 1.1.7-SNAPSHOT
Status: Resolved
Argh, you're right Cagatay. There was one piece of functionality added
since the last time I checked to comply with a recent edition of the
public review. It broke things. Let me see if I can fix it an
regenerate the artifacts. It fails when running with jetty as well.
Good Catch.
[
https://issues.apache.org/jira/browse/TOMAHAWK-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626437#action_12626437
]
Leonardo Uribe commented on TOMAHAWK-1316:
--
I have tried with myfaces core
[
https://issues.apache.org/jira/browse/MYFACES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626436#action_12626436
]
Leonardo Uribe commented on MYFACES-1603:
-
I have tried with myfaces core 1.1.6
21 matches
Mail list logo
