this is amazing! I will play with it if it's possible to visualize the
geographic distribution of media resources that are available in libraries
for access.
Many thanks!
Jörg
On Saturday, November 17, 2012 3:20:34 AM UTC+1, Eric Jain wrote:
Here's a (somewhat simplistic) facet that clusters geo_points:
This looks great! I'm definitely going to take this for a spin, and I'll try to contribute back any fixes/changes we make.
Slightly OT: I haven't done any Java for about 8 years. Things are a little different now on the build front (maven/pom.xml etc). Do you have any pointers for someone like me to update their knowledge of modern Java development tools? (Or, put another way, what's the best place for me to learn how to wrangle a pom.xml )
Slightly OT: I haven't done any Java for about 8 years. Things are a little
different now on the build front (maven/pom.xml etc). Do you have any
pointers for someone like me to update their knowledge of modern Java
development tools? (Or, put another way, what's the best place for me to
learn how to wrangle a pom.xml )
Checking out a project and then building it with Maven from the
command line is simple enough (i.e. mvn package). Just don't attempt
to customize the build process
I use Eclipse with the m2eclipse plugin [M2Eclipse | M2Eclipse].
This plugin can generate the .project and .classpath files for Eclipse
from the pom.xml. It also provides a graphical editor for the pom.xml
and can run builds from within Eclipse.
clone the git repo of the ES plugin. If you want to maintain a branch
with your changes to get integrated into the main development later, fork
it. Check Fork a repo - GitHub Docs
ES builds use Maven right now. Maven is a project management tool with
pros & cons, but the strength is, it can be also invoked from command line
(without IDE) but also a lot of good IDE integrations are available, so
developers can easily step in into the ES development by firing up their
favorite IDE
the easiest method to start development with an ES plugin in my opinion
is provided by Netbeans. Netbeans comes with embedded mvn and git
out-of-the-box. Just download Netbeans from Apache NetBeans Releases I prefer the "full" package because I like
the integration of Java EE, Glassfish, Groovy, and PHP, but "Netbeans Java
SE" is enough for ES plugins.
in Netbeans, select "Open Project" and select the ES plugin directory,
then open it. Netbeans detects Maven projets automatically. That's it.
Refer to the Netbeans menu how to build the plugin with the IDE.
Most important Maven commands are:
mvn clean -> remove all temporary build files and artifacts
mvn clean test -> build the plugin as a JAR, run tests, do not install
mvn clean install -> build the plugin as a JAR, create a ZIP artifact, and
install all artificats into your local Maven repo
You can examine the pom.xml and play with it to find out how it works.
There is a huge amount of complexity behind Maven builds, but ES builds
only exploit a few of them.
The plugin release artifact is a ZIP file in the target/releases folder.
You can take this file to install it into your ES instance. Under ES_HOME,
you can create a "plugins" folder with a plugin named subfolder (e.g.
$ES_HOME/plugins/facet-geocluster). Unpack your plugin ZIP file at this
location before starting the ES instance with ./bin/elastisearch -f. Check
the second line of the log lines for the successful loading of the plugin.
Stop ES and start ES again when updating your plugin.
These are just the basic steps to deploy a plugin, I hope this helps to get
you started.
Cheers and happy building,
Jörg
On Saturday, November 17, 2012 8:10:45 PM UTC+1, Dan Fairs wrote:
This looks great! I'm definitely going to take this for a spin, and I'll
try to contribute back any fixes/changes we make.
Slightly OT: I haven't done any Java for about 8 years. Things are a
little different now on the build front (maven/pom.xml etc). Do you have
any pointers for someone like me to update their knowledge of modern Java
development tools? (Or, put another way, what's the best place for me to
learn how to wrangle a pom.xml )
clone the git repo of the ES plugin. If you want to maintain a branch with your changes to get integrated into the main development later, fork it. Check Fork a repo - GitHub Docs
ES builds use Maven right now. Maven is a project management tool with pros & cons, but the strength is, it can be also invoked from command line (without IDE) but also a lot of good IDE integrations are available, so developers can easily step in into the ES development by firing up their favorite IDE
the easiest method to start development with an ES plugin in my opinion is provided by Netbeans. Netbeans comes with embedded mvn and git out-of-the-box. Just download Netbeans from Apache NetBeans Releases I prefer the "full" package because I like the integration of Java EE, Glassfish, Groovy, and PHP, but "Netbeans Java SE" is enough for ES plugins.
in Netbeans, select "Open Project" and select the ES plugin directory, then open it. Netbeans detects Maven projets automatically. That's it. Refer to the Netbeans menu how to build the plugin with the IDE.
Most important Maven commands are:
mvn clean -> remove all temporary build files and artifacts
mvn clean test -> build the plugin as a JAR, run tests, do not install
mvn clean install -> build the plugin as a JAR, create a ZIP artifact, and install all artificats into your local Maven repo
You can examine the pom.xml and play with it to find out how it works. There is a huge amount of complexity behind Maven builds, but ES builds only exploit a few of them.
The plugin release artifact is a ZIP file in the target/releases folder. You can take this file to install it into your ES instance. Under ES_HOME, you can create a "plugins" folder with a plugin named subfolder (e.g. $ES_HOME/plugins/facet-geocluster). Unpack your plugin ZIP file at this location before starting the ES instance with ./bin/elastisearch -f. Check the second line of the log lines for the successful loading of the plugin. Stop ES and start ES again when updating your plugin.
These are just the basic steps to deploy a plugin, I hope this helps to get you started.
Cheers and happy building,
Jörg
On Saturday, November 17, 2012 8:10:45 PM UTC+1, Dan Fairs wrote:
This looks great! I'm definitely going to take this for a spin, and I'll try to contribute back any fixes/changes we make.
Slightly OT: I haven't done any Java for about 8 years. Things are a little different now on the build front (maven/pom.xml etc). Do you have any pointers for someone like me to update their knowledge of modern Java development tools? (Or, put another way, what's the best place for me to learn how to wrangle a pom.xml )
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.