Meta:maven

Disclaimer: This page is definitely still a work in progress

Normal Process

Maven normally gets all dependencies from the maven central repository. So things like Log4j are automatically downloaded and installed in your local maven cache (.m2 folder in your home directory for *nix). The issue is that we have some dependencies that cannot be found on the central repo for varying reasons (i.e. their package maintainers didn't spend the time to do so, licensing issues, etc). A normal couse of action to get around this is to have each developer manually install the libraries themseleves. This sucks. So to circumvent that, we created our own maven repository hosted on an s3 share on Amazon. This repository is used as an intermediate by maven. The general gist is that when searching for a dependency, it can now search your local .m2 directory, then search our private maven repo and then finally using the central maven repo. This allows us to keep all dependencies easily up to date and makes bringing in new developers easy as the setup process is kept minimal.

TODO

• show how this is done configuration wise
• what do people have to do to add to the maven repo
• etc

Relevant Resources

• handy tool for interacting with s3 buckets
• hosting a maven repo