Our archetype poms are not entirely correctly understood by Netbeans
Key: MYFACES-2933
URL: https://issues.apache.org/jira/browse/MYFACES-2933
Project: MyFaces Core
Issue
[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916429#action_12916429
]
Werner Punz commented on MYFACES-2933:
--
Ok addendum if we do it the activeByDefault
[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916433#action_12916433
]
Werner Punz commented on MYFACES-2933:
--
Ok netbeans does following at context
[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916437#action_12916437
]
Werner Punz commented on MYFACES-2933:
--
Ok I think the best solution would be just
Unsynchronized access to the cache of ThemeConfig
-
Key: TOBAGO-921
URL: https://issues.apache.org/jira/browse/TOBAGO-921
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
[
https://issues.apache.org/jira/browse/TOBAGO-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916440#action_12916440
]
Udo Schnurpfeil commented on TOBAGO-921:
Here is the code I call one time in each
Hi, all,
I've found a new critical bug:
https://issues.apache.org/jira/browse/TOBAGO-921
I've fixed it, but it is not in 1.0.30. So we have two possibilities:
1. put it in 1.0.30 and rebuild it or
2. put it in 1.0.31 and release it asap.
Regards
Udo
Am 29.09.10 09:20, schrieb Bernd
[
https://issues.apache.org/jira/browse/TOBAGO-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-921.
Resolution: Fixed
Unsynchronized access to the cache of ThemeConfig
[
https://issues.apache.org/jira/browse/TOBAGO-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916440#action_12916440
]
Udo Schnurpfeil edited comment on TOBAGO-921 at 9/30/10 10:07 AM:
[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916480#action_12916480
]
Leonardo Uribe commented on MYFACES-2933:
-
Hi Werner
There is no problem.
[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916483#action_12916483
]
Jakob Korherr commented on MYFACES-2933:
IMO this is a NetBeans bug and we don't
+1
Am 28.09.10 02:42, schrieb Leonardo Uribe:
Hi,
I was running the needed tasks to get the 1.1.10 release of Apache
MyFaces Tomahawk out.
Release notes can be found at [4].
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.tomahawk
Changes to UIXIterator break full visiting
--
Key: TRINIDAD-1932
URL: https://issues.apache.org/jira/browse/TRINIDAD-1932
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.0.3-core
Side-channel timing attack in StateUtils class may still allow padding oracle
attack
Key: MYFACES-2934
URL: https://issues.apache.org/jira/browse/MYFACES-2934
[
https://issues.apache.org/jira/browse/MYFACES-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916595#action_12916595
]
Leonardo Uribe commented on MYFACES-2934:
-
I have checked it and well, the
[
https://issues.apache.org/jira/browse/TRINIDAD-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916620#action_12916620
]
Andrew Robinson commented on TRINIDAD-1930:
---
Do we need the more verbose
Changing from 'break;' to 'continue;' is the most straightforward
fix, but I'd recommend adding a comment as to WHY you are doing
this, so that later on, someone doesn't come back to optimize
the code and change it back to 'break'. I'd just put something like
this at the beginning of the 'for'
[
https://issues.apache.org/jira/browse/TRINIDAD-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916634#action_12916634
]
Matt Cooper commented on TRINIDAD-1930:
---
+1; type instead of nameType works for
Hi,
Leonardo, can you please review :
https://issues.apache.org/jira/browse/MYFACES-2922
https://issues.apache.org/jira/browse/MYFACES-2862
and apply them if they are suitable?
Thanks,
Kočičák
Martin Koci píše v Út 14. 09. 2010 v 23:05 +0200:
Hi,
please review
BTW, if you want, feel free to bump this down in priority.
I had no idea of what criteria you use in determining them,
so I just left it at its default, which I think was 'Major'.
Also, I figured 2d was max time, including testing, re-packaging,
etc. since fix was so easy. Maybe I should have
Hi
Ok. I'll lower the priority. I don't think a release is necessary for this
one, so I'll just fix it on trunk. Thanks for your help.
regards,
Leonardo
2010/9/30 Wall, Kevin kevin.w...@qwest.com
BTW, if you want, feel free to bump this down in priority.
I had no idea of what criteria you
Hi
Yes, sure!. Give me some time, right now I'm doing some stuff related to
@ListenerFor annotation, so as soon as I'm done I'll take a look.
regards,
Leonardo
2010/9/30 Martin Koci martin.kocicak.k...@gmail.com
Hi,
Leonardo, can you please review :
MArtin,
your account is now setup - you even could apply them yourself,
after Leo did a successful review
-;M
On Thu, Sep 30, 2010 at 1:14 PM, Martin Koci
martin.kocicak.k...@gmail.com wrote:
Hi,
Leonardo, can you please review :
https://issues.apache.org/jira/browse/MYFACES-2922
Hi,
there is a disorder in Expression Lauguage names in myfaces core.
Currently myfaces (method
javax.faces.validator._ExternalSpecifications.isUnifiedELAvailable() for
example) output a log:
MyFaces Unified EL support enabled
But this is a little misleading: there should be Unified EL 2.2
[
https://issues.apache.org/jira/browse/TRINIDAD-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916667#action_12916667
]
Matt Cooper commented on TRINIDAD-1930:
---
Other changes for consistency with other
[
https://issues.apache.org/jira/browse/TRINIDAD-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Cooper resolved TRINIDAD-1930.
---
Fix Version/s: 1.2.14-core
2.0.0.2-core
Resolution: Fixed
[
https://issues.apache.org/jira/browse/MYFACES-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2934.
-
Assignee: Leonardo Uribe
Fix Version/s: 1.1.9-SNAPSHOT
[
https://issues.apache.org/jira/browse/MYFACES-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916754#action_12916754
]
Leonardo Uribe commented on MYFACES-2509:
-
Attached patch with some changes and
Hi
Both optimizations are ok. +1
If you want I can commit it but I suggest you commit them.
regards,
Leonardo
2010/9/30 Matthias Wessendorf mat...@apache.org
MArtin,
your account is now setup - you even could apply them yourself,
after Leo did a successful review
-;M
On Thu, Sep 30,
Hi
2010/9/30 Martin Koci martin.kocicak.k...@gmail.com
Hi,
there is a disorder in Expression Lauguage names in myfaces core.
Currently myfaces (method
javax.faces.validator._ExternalSpecifications.isUnifiedELAvailable() for
example) output a log:
MyFaces Unified EL support enabled
But
Hi
Thanks to all people who vote
We have 3 +1
Werner Punz
Jakob Korherr
Leonardo Uribe
So we can continue with the necessary steps to release tomahawk 1.1.10
regards,
Leonardo
SystemEvent Acid Test
-
Key: MYFACES-2935
URL: https://issues.apache.org/jira/browse/MYFACES-2935
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2
Reporter:
Ok
I'm for the option 1. So I cancel this vote and create a new vote.
Regards
Bernd
On Thu, Sep 30, 2010 at 4:05 PM, Udo Schnurpfeil u...@schnurpfeil.de wrote:
Hi, all,
I've found a new critical bug:
https://issues.apache.org/jira/browse/TOBAGO-921
I've fixed it, but it is not in 1.0.30.
33 matches
Mail list logo