I see from the commit list that a new JSF2.0 branch has been created.
I don't remember seeing *any* kind of discussion or even announcement
about this. While I am happy to see JSF2.0 work going on, this kind of
approach does not seem to be at all in the "community" spirit. IMO,
major events li
Add resetValue() to EditableValueHolder interface (this is a JSF 2.0 related
issue)
---
Key: MYFACES-1910
URL: https://issues.apache.org/jira/browse/MYFACES-1910
Project:
Great.
Manfred/others, I think we should already create a "component" in JIRA
for JSF.next
-Matthias
On Thu, Aug 28, 2008 at 12:31 AM, Simon Lessard (JIRA)
wrote:
> Implement JSF 2.0 Early Draf 2008-04-21
> ---
>
> Key: MYFACES-1909
>
[
https://issues.apache.org/jira/browse/MYFACES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626436#action_12626436
]
Leonardo Uribe commented on MYFACES-1603:
-
I have tried with myfaces core 1.1.6 a
[
https://issues.apache.org/jira/browse/TOMAHAWK-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626437#action_12626437
]
Leonardo Uribe commented on TOMAHAWK-1316:
--
I have tried with myfaces core 1.1.
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.
Cagata
[
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 (wa
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
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 con
[
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
[
https://issues.apache.org/jira/browse/TRINIDAD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626305#action_12626305
]
Simon Lessard commented on TRINIDAD-205:
It's true that an interface would be cle
Firefox warns about Error in parsing value for property 'cursor'. Declaration
dropped.
---
Key: TOMAHAWK-1320
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1320
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?
>
>
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?
http://wiki.apache.org/myfaces/SecurityContext
Cagatay
+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
+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:0
I'm using Pluto 1.1.6 with tomcat6 as the test environment.
After replacing alpha-2 jars with alpha-3 jars for my portlet, I got;
Caused by: java.io.IOException: Unable to process response. Failed to
locate SAVESTATE_FIELD_MARKER
at
org.apache.myfaces.portlet.faces.application.PortletViewHan
+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,
>>>
+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 needed tasks to get the 1.2.4 release of Apache
>> MyFaces core out.
>>
>> The artifact
On Wed, Aug 27, 2008 at 1:07 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote:
> 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
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 "org.apache.myfaces
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 exam
[
https://issues.apache.org/jira/browse/TRINIDAD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626194#action_12626194
]
Jeanne Waldman commented on TRINIDAD-205:
-
I looked at the code briefly and it lo
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:
https://issues.apache.org/jira/secure/ReleaseN
[
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
1.2.10
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626109#action_12626109
]
Matthias Weßendorf commented on TRINIDAD-1195:
--
I am sorry to say, that I a
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626100#action_12626100
]
Stephen Friedrich commented on TRINIDAD-1195:
-
No, this is not a seam issue.
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 PROT
[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625993#action_12625993
]
Matthias Weßendorf commented on TRINIDAD-1195:
--
Tested this (in JSPX):
[
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
1.2.10-c
+1
On Wed, Aug 27, 2008 at 4:48 AM, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to release the MyFaces Portlet Bridge Master 1.0.0-alpha-3.
> This pom file was created in order to support the latest JSR-301 Public
> Review so that it may be tested by developers during the review
31 matches
Mail list logo
