remove commented code in RubyPathname
always map ENOSYS to NotImplementedError

* since this is basically what it means, but the headers still define the function
* this is to have similar feature to configure MRI tests and rb_f_notimplement
Fix parameter passing to procified method. JRUBY-6763.
relocate objectweb classes into org.jruby.org.objectweb
use compiler plugin 2.5.x to have proper incremental compilation
Revert "use compiler plugin 2.5.x to have proper incremental compilation"

just breaks travis :(

This reverts commit 3f93c50aa743aec03d6b93f4eeecea804ff1dc2c.
Move Maven site reporting to parent pom. Fixed parent hierarchy.
Remove reminisce of build_lib from eclipse .classpath
Add joda-time to jruby-core pom.xml to get build working with clean checkout
Merge pull request #864 from jendave/maven-reporting

Move Maven site reporting to parent pom. Fixed parent hierarchy.
Use <pluginManagement> in parent pom so that all plugins (and their versions) for the project can be centrally managed. All Maven plugins are now consistent (where necessary) throughout the project.
Use <pluginManagement> in parent pom so that all plugins (and their versions) for the project can be centrally managed. All Maven plugins are now consistent (where necessary) throughout the project.
Merge branch 'plugin-management' of https://github.com/jendave/jruby into plugin-management
Enable incremental compilation.

Don't look at me like that.
Add threads 1-by-1 to ThreadGroup.list, to avoid adding a null.

Because RubyThread objects are held in a weak set inside
ThreadGroup, blindly copying them into an array *might* cause us
to insert a null somewhere. This new logic at least ensures that
does not happen, though it may not fix @halorgium's issue reported
on IRC today.
Temporarily rename problematic remove method to removeFrom.

Final decision about how to fix this still remains with @yokolet

See #858.
removed obsolete second shade and give tzdata another trial to get it right
also the test profile does not need joda time anymore
Fixed a bug in checking the type of edges in EdgeTypeIterator

- While checking for type of edges, equality is not sufficient as we
  are comparing two objects
- Added specs for this change
Merge pull request #852 from prathamesh-sonpatki/vertext_specs

Fixed a bug in checking the type of edges in EdgeTypeIterator