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.

Reply via email to