make the jar manager to have some of the checks already present in the old load_elasticsearch_jars
removed the load_elasticsearch_jars! method as it's a legacy code from when ES was delivered within LS, nowadays this comes within the differents plugins
clean up Environment::JAR_DIR as is another legacy variable not used anymore
move the jar loading code within the environment module
ammend previous commit adding more clear code
ammend previous commits
added a few simple unit test for the jar manager in the environment module
refactor spec naming
dry out common code for loading jars
clean up env_spec bein in the util dir
cleaning up logstash-core dependencies related to jar-dependencies
ammend stale maen patches created for the LS way of using maven plugins
applied some comments coming from the review by @ph
bring back the maven tools and jar-dependency code as we still need some code like this for the kafka plugins
Revert "bring back the maven tools and jar-dependency code as we still need some code like this for the kafka plugins"
This reverts commit c23f456362776c0a600d78369c2ece8789fa49c2.
Fixes#2980
There's several indications that folks don't actually read this banner
when unexpected errors occur. If nobody's reading it, then it's just
wasting space in the output.
I would cite references, but will not because there's no need to shame
anyone.
Fixes#1442
future.
agent2 should now successfully use the new config parser w/ codec
support.
No 'conditionals' support yet, but I will add that soon.
Rough list of changes:
- try to unify agent2 errors
- make codecs loaded the same way other plugins are (removes extlib,
woot)
- make default values subject to validation (necessary for codecs)
- some style cleanup
- move more error messages into locales/en.yml
- fix LogStash::Event#to_s to use %{+...}
- log backtraces from the agent if debug (-vv)
- more friendly error messages
- style tweaks to stdin plugin
- copy parse_config into agent2
- improve pipeline shutdown under agent2
Notable big changes is that I try to offer suggestions as to what might
be wrong. Additionally, for unrecoverable failures, emit a big message
about how this is probably a bug and offer irc/mailing list/etc
