Yes Richard you are right but: date of issue 2009/09/19 and Original estimate 168hs and 10 votes
I don't think we will see it fixed for NH3 release. On Mon, Aug 2, 2010 at 9:27 AM, Richard Brown (gmail) < [email protected]> wrote: > Presumably there's no logging work for us to do if log4net can target the > ClientProfile too? > > https://issues.apache.org/jira/browse/LOG4NET-233 > > > *From:* Fabio Maulo <[email protected]> > *Sent:* Monday, August 02, 2010 1:25 PM > *To:* [email protected] > *Subject:* Re: [nhibernate-development] Re: Logging Abstraction > > The place to vote for issue fix is our JIRA > http://216.121.112.228/browse/NH-2263 > > Thanks. > > Here we can discuss about some "long" implementation details. > > On Mon, Aug 2, 2010 at 8:03 AM, David Pfeffer <[email protected]> wrote: > >> I personally find the client profile support extremely important -- once >> its available, I'll immediately begin using it. NHibernate is my only >> dependency forcing me not to use the client profile. >> >> On Mon, Aug 2, 2010 at 7:01 AM, Craig van Nieuwkerk >> <[email protected]>wrote: >> >>> I think client profile will become much more important in the future. >>> It is only just becoming used frequently with .NET 4 and I suspect >>> most desktop applications will soon prefer it. If the work required >>> doesn't require major rewriting I would say go for it, especially if >>> Patrick is happy to do most of the leg work. >>> >>> Craig. >>> >>> On Mon, Aug 2, 2010 at 8:56 PM, Fabio Maulo <[email protected]> >>> wrote: >>> > Patrick, >>> > Are you sure that the client-profile-support is so fundamental ? >>> > So far you are the only one talking about it. >>> > Before begin a big work in NH-3 I would be sure about how much >>> important is >>> > the client-profile-support for NH future. >>> > >>> > On Mon, Aug 2, 2010 at 6:34 AM, Patrick Earl <[email protected]> wrote: >>> >> >>> >> For myself, I'm not particularly opinionated in any direction other >>> >> than the direction that will allow for client profile support. If >>> >> this happens through a custom pluggable logging layer, common.logging, >>> >> or some other way, I'm happy. It seems like the common.logging >>> >> library is a good fit, but it's not already on the trunk so I'd be >>> >> curious to know why. >>> >> >>> >> The last log4net release was in 2006 and the mailing list is pretty >>> >> quiet in terms of "getting it done" type traffic. It also seems like >>> >> over time there has been not insignificant demand for the ability to >>> >> use a different logging framework. Using something like >>> >> Common.Logging seems like a good way to solve the problems with the >>> >> client profile dependencies and the different logging framework >>> >> support. >>> >> >>> >> I don't think that replacing log4net with Common.Logging is like >>> >> trading one "evil" for another. Common.Logging has a much smaller >>> >> footprint than the actual logging frameworks and was designed to solve >>> >> the pluggable logger problem. If this is what is desired for >>> >> NHibernate, why not utilize the work of others? On top of this, there >>> >> is already a patch to implement this change in NHibernate. >>> >> >>> >> I'd very much like to have this issue pushed to completion. If it >>> >> involves additional development, testing, or documentation time, I >>> >> would be happy to volunteer my time. I just need to know where to put >>> >> my energy. >>> >> >>> >> Patrick Earl >>> > >>> > >>> > -- >>> > Fabio Maulo >>> > >>> > >>> >> >> > > > -- > Fabio Maulo > > -- Fabio Maulo
