sure thing, might not get to it for a bit...kinda crushed under some other things but definitely something interesting to look into.
I was just thinking, that perhaps instead of domaining by package, it might be interesting to try and do it via artifact...I am not sure what kind of overhead would be involved, but getClass().getResource() works for pulling out of the jar you are a part of...so we ought to be able to discover the artifact pretty easily. Probably not something we want to do every log hit but some kinda singleton in the plexus logging might be able to manage it... but by domaining by artifact, you could have the added benefit of logging context of artifact interaction and by grepping out on a particular artifact get all of the dealings in that particular artifact. just a thought jesse On 1/11/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > Jason van Zyl wrote: > > That would be cool! It would be far simpler for users to track down > > specific problems and even if there are intersecting domains involved > > you just turn on the logging for the appropriate domain. Very nice idea. > > Agreed. So how do we go about this? We can probably match the package > name to a domain, but I'm not sure how we then rename that and get the > plexus logger to spit it out. > > Jesse, are you interested in investigating? > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom
