I propose making Eelco a committer. I'm +1.
Jeff > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:mav-user- > [EMAIL PROTECTED] On Behalf Of Eelco Hillenius > Sent: Tuesday, June 01, 2004 11:58 AM > To: [EMAIL PROTECTED] > Subject: Re: [Mav-user] Use Apache Commons Logging instead of log4j > > If you'd give me commit rights I would be happy to do the dirty work ;) > > Eelco (sf id eelco12) > > ----- Original Message ----- > From: "Schnitzer, Jeff" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, June 01, 2004 8:33 PM > Subject: RE: [Mav-user] Use Apache Commons Logging instead of log4j > > > +1 on moving to commons-logging > -1 on moving to JDK1.4 logging > > What problems are there running Maverick on JDK1.3? The only tricky > thing is making sure you have an XML parser since it isn't builtin. > > The only thing preventing a move from log4j to commons-logging was the > absence of anyone who actually wanted to use it that way (as opposed to > a bunch of people, including myself, who just think it might be a good > idea). We try to follow the XP YAGNI principle, which is why Maverick > is as simple as it is. > > It sounds like we now have a customer for that change. > > Do we have a volunteer to do the conversion? > > Jeff > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:mav-user- > > [EMAIL PROTECTED] On Behalf Of Scott Hernandez > > Sent: Tuesday, June 01, 2004 11:11 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [Mav-user] Use Apache Commons Logging instead of log4j > > > > Sure. +1 to changing package names and moving to commons logging, or > java > > 1.4 logging (I think we may have some problems running on 1.3 anyway, > or > > was > > it just some of our dependencies...). > > > > It would probably be good to roll any good questions that have come up > on > > the list into the faq, and documentation. > > > > We should get a list of changes together, but patches are always > welcome. > > :) > > > > ----- Original Message ----- > > From: "Mike Moulton" <[EMAIL PROTECTED]> > > > > > > There have been a few global changes that have been pending for a > > while. For instance there was the discussion of repackaging everything > > to net.sf.mav.*. If I'm not mistaken there were a few other changes as > > well. Maybe now would be an appropriate time to readdress some of the > > changes including this logging change. > > > > I don't see any major problems switching to commons logging, > personally > > I will still use log4j. > > > > Thought, Jeff, Scott, Jim? > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: Oracle 10g > > Get certified on the hottest thing ever to hit the market... Oracle > 10g. > > Take an Oracle 10g class now, and we'll give you the exam FREE. > > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > > [INVALID FOOTER] > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id149&alloc_id66&op=ick > [INVALID FOOTER] > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > [INVALID FOOTER] ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 [INVALID FOOTER]
