Hi,
I've been hacking the
org.apache.myfaces.shared_impl.renderkit.html.HtmlFormRendererBase, and even
commented out the whole thing, and my forms were still rendering fine...because
I was hacking the one in the
org.apache.myfaces.shared.renderkit.html.HtmlFormRendererBase, when I should
hav
Hello,
I agree with Simon, too. All MyFaces projects should use one logging
impl. But this doesn't mean we should stay with commons-logging.
Since a half year slf4j is on my wish list. But I don't interested in a
slf4j vs commons-logging battle.
slf4j has a better api compare to commons-logging.
The vote has passed with the following votes:
+1
lofwyr (binding)
grantsmith (binding)
weber (binding)
idus
bommel (binding)
mmarinschek (binding)
I will proceed with the next steps.
Regards
Bernd
Bernd Bohmann schrieb:
> Hello,
>
> I would like to release Tobago 1.0.13,
>
> This release
and finally here is my
+1
Regards
Bernd
Arvid Hülsebus schrieb:
> +1
>
> I tested 2 of my small apps... everything looks fine.
>
> Regards,
> Arvid
>
> Udo Schnurpfeil wrote:
>> +1
>>
>> Gegards
>>
>> Udo
>>
>> Martin Marinschek schrieb:
>>> +1
>>>
>>> regards,
>>>
>>> Martin
>>>
>>> On Dec
Leonardo,
Sorry for answering so late. I had to go through a two weeks backlog
in my inbox. And two weeks means a huge load when subscribed to
MyFaces lists... ;-)
Anyway, to give you as much help as possible I started a new wiki page
at the Vienna Hackthon:
http://wiki.apache.org/myfaces/Release
I agree with Simon, that all MyFaces projects need to use one logger.
That said, we must assume that application developers using MyFaces
projects will not use the same logger that MyFaces uses. Thus the
logger we use should be pluggable so the application developer can use
one logger for his
[
https://issues.apache.org/jira/browse/TRINIDAD-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552219
]
Matthias Weßendorf commented on TRINIDAD-768:
-
applied to 1.0.x trunk;
I'll apply it to 1.2.x on Monday
[
https://issues.apache.org/jira/browse/TRINIDAD-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-860:
Resolution: Fixed
Fix Version/s: 1.2.5-core
1.0.5-core
yes, "myfaces-build-tools" is a much better name
--Manfred
On 12/16/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
> +1 About the naming, though, this seems to be more myfaces-build-tools
> than myfaces-dev-tools, because as far as I understand, this artifacts
> are used during the build, not for j
On Sun, 2007-12-16 at 12:07 +0100, Bernd Bohmann wrote:
> Hello,
>
> i think slf4j is a better alternative for logging compare to
> commons-logging. I don't like to start a slf4j vs commons-logging battle.
>
> Just ask google.
>
> I will change the tobago logging to slf4j.
Asking google is a v
Hello,
i think slf4j is a better alternative for logging compare to
commons-logging. I don't like to start a slf4j vs commons-logging battle.
Just ask google.
I will change the tobago logging to slf4j.
Regards
Bernd
Mario Ivankovits schrieb:
> hi,
>
> basically yes, thats what I thought.
> N
Replace commons-logging with slf4j
--
Key: TOBAGO-576
URL: https://issues.apache.org/jira/browse/TOBAGO-576
Project: MyFaces Tobago
Issue Type: Improvement
Reporter: Bernd Bohmann
Assig
hi,
basically yes, thats what I thought.
Not sure if registering resource bundles is the way to go as this leads to
duplicate/overridden keys then. Think what happens if you have 80+ libraries
everyone registering a resource bundle.
Thats why I thought it should be the responsibility of the app
Hi Mario,
You mean a myfaces-commons-logging module, that the following depend on?
* myfaces-commons-*
* myfaces-core
* myfaces-trinidad
The problem again is that each of those has its own resource bundle for
its messages, and that there would need to be some mechanism for it to
inform the myf
14 matches
Mail list logo