eventbus.publish shouldn't accept a reply handler
Support public ip & port for event bus clustering
  - This is handy when you bind to an ip/port that is not accessible by other members of the cluster
when redeploying modules make sure we select the top most *not raw verticle* deployment
Merge pull request #761 from nscavell/openshift

Support public ip & port for event bus clustering
Merge pull request #747 from larrytin/master

eventbus.publish shouldn't accept a reply handler
updated CONTRIBUTING.md with complete instructions for committing
updated CONTRIBUTING.md with complete instructions for committing
updated CONTRIBUTING.md with complete instructions for committing
eventbus.publish shouldn't accept a reply handler
updated CONTRIBUTING.md with complete instructions for committing
updated CONTRIBUTING.md with complete instructions for committing
updated CONTRIBUTING.md with complete instructions for committing
Implement module links functionality
Merge branch 'module-link'
Added command line help for create-module-link
make doLoadClass synchronized to prevent same class being defined twice when similar verticles deployed concurrently
added module field load-from-module-first which allows module classloade load order to be reversed - this is useful if your module contains different versions of the same jars that are used by Vert.x itself - e.g. Hazelcast or Netty
some tweaks to redeploy and ignore comments and blank lines in vertx_classpath.txt
Make sure we watch any urls from included modules too for auto-redeploy
re-instate synchronized which I reverted in a previous commit