vert-x/vert.x — pull request #316 by blalor (2012-08-03 15:34:23+00:00)
Title: Maven build implementation

For your consideration.

The distribution archive is not yet complete. Python documentation is lacking. Deploying to Maven Central is not yet configured. This is, however, a standard Maven build. `pom.xml` files have been added, and `JRubyVerticleFactory.java` was tweaked to not throw an exception if `JRUBY_HOME` is not set. No changes have been made to the Gradle build; I was happy to see that they essentially follow the same conventions. No Maven plugins needed to be created, but I did make liberal use of the [Maven Antrun plugin](http://maven.apache.org/plugins/maven-antrun-plugin/) to integrate with JRuby and generate the Groovy docs. I intend to something similar for the Python docs.

From the project root run `mvn package` to create the distribution directory in `distribution/target/distribution-1.2.4-SNAPSHOT-bin`. Throw `-DskipTests=true` on there if you want to bypass the tests in `vertx-testsuite`, which will otherwise run by default. If you want to mess with the distribution module, first do a `mvn install` in the project root (this copies the artifacts into `${user.home}/.m2/repository`, where other artifacts are downloaded), and then you can invoke `mvn package` from the `distribution` directory. The top-level `mvn package` works because Maven is considering the entire project structure with all child modules in the "reactor" when resolving dependencies.

If you'll help me understand the tasks you perform on a daily basis, as well as your release process, I can show you how to accomplish those same things with the Maven build.