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
Disentangle ProxyRepoDownloadTest from RepoDownloadTest

Turns out that the Proxy test only worked because the RepoDownloadTest
had already downloaded the test app and therefore it never actually
hit the proxy server. If it did, it would have noticed that it tried
to hit it with a relative url first (because localhost:9193 is in the
list of repo resolvers) and then tried a wrong url (ending in :9193,
not in :9192).

Run the proxy on another port (9194), fix the request URI using 9193,
change the name of the proxy app to not be the same as the non-proxy
download app.

Both ProxyRepoDownloadTest and RepoDownloadTest are still stateful
tests because if they are run multiple times without cleaning out the
mod-test folder, the test will not hit the actual server the second
and any further time.
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
Use var pingInterval as parameter of setInterval

Signed-off-by: Larry Tin <dev@goodow.com>
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