Github user cestella commented on the issue:
https://github.com/apache/metron/pull/755
Ok, I just want to be completely clear, we're actually choosing *one* of
our jars, the parsers jar, because it's an uber jar that has ALL of our stellar
functions in Metron in it. I'm also providing explicit support for the
management functions. This should make our classpath more deterministic, I
think, and provide a mechanism that is more flexible for passing in custom jars
(the env variable, rather than presuming users would drop things in
`$METRON_HOME/lib`.
---
