Just a FYI, that dependency is now solved.

> How, using yet another logging wrapper? If so, another rant is about to errupt.

I need to support some logging within JBossSerialization, as a way I (or future contributors) could debug it.

If you define org.jboss.serial.LogLevel=5 it will enable tracing on JBossSerialization. There is a class doing that parsing:

org.jboss.serial.util.Logger

The wrapper is pretty small, is more an utility class.

I didn't like the solution itself. Still looking for a better way to do it:

The reason that I wanted to avoid using jboss-common and log4j was just to make easier using JbossSerialization outside of JBoss. (just add a JAR and import the correct package)

Well... as I know you (and everybody else) is going to complain about it, I'm going to change it. lol

I will try to keep using log4j and jboss-commons, but testing for classes availability. (like, if not available, just disabling log).

I will probably need to work with Object on the logger, and create a small parser just to do the type cast.



public class SomeClas
{
public static Object logger;
public static boolean isLog;

static
{
// some initialization on the logger
}


public void someMethod()
{
if (isLog) // just to no test for the type if don't need to
{
LoggerWrapper.log(logger,message);
}
}
}


The LoggerWrapper will deal with conversions, using reflection so I could have jboss-serialization.jar without having log4j.jar and jboss-commons.jar on the classpath.