Use deterministic prefix in loggerName so level can be configured

Without a common hierarchy for the name of a logger, its level cannot be set granularly.  Without this, if I wanted to enable INFO for a JavaScript verticle's logger, I'd have to configure the entire application's root level to INFO or lower.  This still doesn't address the fact that you can't configure a specific logger (because you can't set the logger's name externally), but that would require another deploy-time config param.
Merge pull request #390 from blalor/logger_name_hierarchy

Use deterministic prefix in loggerName so level can be configured
Merge pull request #387 from blalor/honor_classpath

Do not overwrite CLASSPATH set externally
Merge pull request #385 from aaboyd/windows_build

Fixing pydoc and yardoc tasks on windows
Merge pull request #388 from blalor/own_log_config

Allow user to specify own j.u.l config
fixed memory leak
fixed mem leaks
Now chooses java factory mapping correctly for Java classes in default package
removed stray log
prepare for 1.3.0. release
Fixed module reloading issues
fix 1.3.0 release
https://github.com/vert-x/vert.x/issues/401
re-initial JMX support
checkpoint
Fix for exception being thrown on programmatic verticle deployment without a done handler
copied changes one more time
added an angularjs example based on the knockoutjs javascript/webapp example
minor changes
fixed test issues in windows. Timing and files not being closed. It's an issue in windows because of the different file system semantics