Is the log4j gem a hard requirement or does log4j just need to be on the classpath

[rtyler]

When using jruby-gradle to build JRuby-based Storm topology jars that need to be uploaded into a running Storm cluster, I've got the challenge of log4j already being pulled in as a transitive dependency of other libraries for the topology jar.

I'm wondering if the require 'log4j' is necessary in java_base.rb or if the requirement is that log4j.jar is somewhere in the JVMs classpath

This is perhaps somewhat related #63

[slyphon]

honestly, it's been over 2 years since I've run the JRuby jar in anger.
Zookeeper has a dependency on log4j being present, so I included it. I'm
not sure what the particulars of the require 'log4j' are in terms of its
effect on the classpath, it's just too long ago for me to remember the
details.

Maybe try running the code sans require line and see what happens?

Sorry I don't have more insight for you.

On Fri, Nov 14, 2014 at 12:12 PM, R. Tyler Croy notifications@github.com
wrote:

When using jruby-gradle to build JRuby-based Storm topology jars that
need to be uploaded into a running Storm cluster, I've got the challenge of
log4j already being pulled in as a transitive dependency of other libraries
for the topology jar.

I'm wondering if the require 'log4j' is necessary in java_base.rb or if
the requirement is that log4j.jar is somewhere in the JVMs classpath

This is perhaps somewhat related #63
#63

—
Reply to this email directly or view it on GitHub
#71.