Consider shipping log4j jar in root lib/ directory

Look into adding a log4 jar to root lib/ directory in distribution in order for modifications to etc/log4j.xml to have immediate effect.

If log4j jar cannot be found, Infinispan uses JDK logging by default and it's not very obvious that a log4j jar is missing and that's why log4j.xml changes have no impact.

This happens with any modules executed except: gui, ec2 and lucene-directory modules.

These modules don't have this issue cos they ship a log4 jar:

./modules/ec2/lib/log4j-1.2.14.jar
./modules/gui/lib/log4j-1.2.14.jar
./modules/lucene-directory-demo/lib/log4j-1.2.14.jar