Overview | Downloads | Quick Start Guide | Installation Guide | API Docs | SourceForge Project |
NOTE: What follows is the full install process. It is very probable that all you need to do is unpack the archive, change into the bin directory and run mgfind.
jar xf moonglow.jar
MOONGLOW_HOME
to the directory
you just created, e.g.: export MOONGLOW_HOME=~/moonglow
[optional] Add $MOONGLOW_HOME/bin
to the path, e.g.
export PATH=$PATH:$MOONGLOW_HOME/bin
[optional] In order to avoid typing these in every time you do a search, you'll probably
want to paste these values into the
$MOONGLOW_HOME/config/client.properties
file, as such:
amazon.devtag=your_devtag
google.devtag=your_devtag
chmod 755 $MOONGLOW_HOME/bin/*
mgfind
, see the quick
start guide for more details.
If you are building from source code, as in a CVS checkout, please follow these steps:
lib
directory of the project to your $ANT_HOME/lib
directory
MOONGLOW_HOME
environment variable to the root of the project (e.g.
export MOONGLOW_HOME=~/moonglow
) and add the bin directory
to your path (e.g. export PATH=$PATH:$MOONGLOW_HOME/bin
).
$MOONGLOW_HOME/config/client.properties
file (for convenience).
If you would like to unit test these plugins against the real servers,
add the devtags to $MOONGLOW_HOME/testdata/test-client.properties
as well, and set the value simserver=false
.
MOONGLOW_HOME
directory and run ant install
.
ant
with no target
to do a clean compile.
Other targets include: test, javadoc, clean, and compile.
.
See build.xml for all targets.
mgfind
, see the quick
start guide. On UNIX, you may need to give execute permissions
to the command-line scripts, i.e.
chmod 755 $MOONGLOW_HOME/bin/*