New structure for getting bootstrapped:

* mvn package will just build enough to execute JRuby. This seems
  more in line with package phase, since phases after this involve
  integration testing.
* Move gem installations to integration-test phase. Ruby tests
  seem more like integration testing, since they're almost all
  hitting large parts of JRuby rather than any single unit. This
  also solves issues with installing gems that depend on a fully
  functional package, like jruby-launcher.
* ant test-extended runs everything up through verify stage, which
  includes integration-test gem installs. It then proceeds to
  run rake test:extended against the fully-bootstrapped JRuby.
* rake test:extended runs unit tests (via -Ptest) and all Ruby
  unit tests, which for our purposes are integration tests.

So the workflow goes like this:

* After a clean checkout of JRuby, or if you want to ensure you
  are properly bootstrapped (with updated gems, for example), you
  would run "mvn verify".
* From that point, all JRuby commands should work, including gem,
  rake, rspec, and so on.
* Subsequent updates to jruby.jar can be achieved with just "mvn
  package" or "mvn", which is reasonably quick.
* Ruby tests can be run via rake, rspec, ant, or mspec.
Remove unused jruby-launcher gem.
Specify max memory for unit test runs.
Increase fork count and do not reuse to give unit tests isolation.
Add BUILDING file to help newcomers get bootstrapped.
Minor tweaks to BUILDING
Remove almost all binaries and switch to maven project.

In detail:

* Remove most jar and gem files from build_lib, since they will
  be sourced via maven.
* Remove nbproject and allow NetBeans to open us as a Maven
  project.
* Remove build.xml references to build_lib binaries
* Remove some ant build targets that are no longer used and/or
  will not work without build_lib present.
Remove remaining binaries from build_lib.

* bnd is now sourced from maven.
* bouncy-castle-java.rb moved under gems/bouncy-castle-java/lib.
* jruby-win32-ole gem will get sourced from maven.

Additional tweaks to get jar-dist working.
Build status should show only the master

…until we branch 1.7
Merge remote-tracking branch 'github/master'
Removed comment about assert[ci skip]

- We are not asserting presence of more than one edge anymore
Eliminate most references to build_lib.
[skip ci] Build instructions are now obsolete
Get dev gems installing properly with removed build_lib.
Merge pull request #844 from prathamesh-sonpatki/remove-assert-comment

Removed comment about assert[ci skip]
Move to @mkristian's proposed layout, with some modifications.
Remove Constants.java from src tree.
get the Constants.java updated with each maven run - added missing pom.xml from ext/maven/docs dir
moved deps from jruby-complete to jruby-core so things compile
Fix copying of .rb sources into jar and path to jruby.home.