> -----Original Message----- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: 04 May 2004 12:03 > To: 'Maven Developers List' > Subject: RE: [maven2] Anything Groovy in Maven2? >
[snip] > > > > commons-logging is the best match I can think of for now. > > > > I don't think it's the best option. > Logging is often used as a substitute for proper exception handling and > for > debugging. I was not referring to exception handling or to debugging. I was referring to the output you see when you run maven for example. Things like the name of the currently executing goal, etc. > With Log4J/JDK Logger and such libraries the problems might appear when > hierarchy of class loaders is more complicated > (this is generally the problem with the singleton design pattern). Design > Patterns like Monitor (that's what was used already in Wagon) seems much > more appropriate and less intrusive. Debugging mode can be also easily > implemented with AOP programming > (all calls to plugins method can be easily registered and written to a > log). I'll need to read more about this Monitor pattern. I don't know what it is. I've seen a blog mentioning it. I have some homework to do :-) AOP is fine for debugging (I have been using AspectJ since 2001 for doing this) but it wouldn't work for info type logging. > > It should be not that hard to do this with plexus and classworlds > (this mode can be enabled on demand when maven is started and bundle of > jars > which allows this can be optional). > I need to do some research to understand all this. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
