IMHO, you don't need maven. You just need the Java trick to include all of the ES dependent jar files by setting the classpath to a colon-separated list of directory names, but append "/*" to the end of each directory name. If you do this, you don't need to list all of the jars in the directory: The jvm will find them for you.
Assume that ES is installed in /somepath and the jar files are in the /somepath/elasticsearch-0.90.9/lib directory. Then your jars are in the /somepath/mystuff/lib directory. Putting them all together: $ java -classpath "/somepath/elasticsearch-0.90.9/lib/*: /somepath/elasticsearch-0.90.9/sigar/lib/*:/somepath/mystuff/lib/*" ... I wrap all this mumbo-jumbo inside Bash scripts. One Bash script to emit the full classpath collection of colon-separated pieces. Then a Bash script that calls it to set up the Java command. Dirt simple. Nice and easy. I can even dynamically re-point to a current build or the installed version for testing current changes and regression-testing the full installation as the customer would see it (respectively). Brian -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7562d544-0547-472b-a1db-4bd9d84fbc13%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
