What you're seeing is the natural result of design conversations held
outside of the mailing list. No one here had the benefit of participating
in the localized logging design so naturally we're asking questions and
making suggestions.
Additionally, it might have helped all of us if the proposal didn't use
marketing hype terms devoid of meaning (ie. "enterprise") to describe what
is actually a small and reasonable set of additions related to localized
messages.
There are no "JSR-mandated logging requirements" for commons logging so
I'm not really sure what that means.
David
--- "Noel J. Bergman" <[EMAIL PROTECTED]> wrote:
> It disturbs me that what seems to me to be a reasonable and small set of
> requirements --- along with what appears to have been considerable
> forethought based upon real world issues, and experiences supporting
> many
> developers --- appears to be discounted a bit too out of hand. I hope
> my
> perception is wrong.
>
> Does anyone really dispute the requirement to support localization for
> log
> messages or the additional JSR-mandated logging requirements? If not,
> then
> let's work constructively towards satisfying the requirements. And not
> by
> relying upon some IDE's tooling.
>
> --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
