Outsourced Operator Type from NumericType to allow for a more fine
Operator structure suggested by @bdezonia:
https://github.com/imglib/imglib2/issues/24
Remove imglib2-algorithms-legacy

In accordance with the discussion at the October 2014 ImgLib2 hackathon
in Madison, this project is being retired. It is not in active use as
far as we know. For anyone still using it: the
net.imglib2:imglib2-algorithms-legacy:2.0.0-beta-26 release will
continue to be available as a stable dependency. If you need to make
code changes to these classes for your project, the suggested approach
is to resurrect them from just prior to this commit, and fork them into
your project with a renamed package.
Remove imglib2-scripting code

A while back, it migrated to its own repository:
  https://github.com/imglib/imglib2-script

This scripting code came back recently due to the merge of a rather old
topic branch. The new package (net.imglib2.script.algorithm.integral),
and related test code being removed here, has all been migrated to the
imglib2-script repository.
Remove imglib2-ops project

It migrated into the ImageJ OPS project as deprecated code:
https://github.com/imagej/imagej-ops/commit/a332184e6014567f47a14276c419f4ac3a0172f6

The goal is to fully replace the functionality of ImgLib2 OPS with that
of ImageJ OPS, according to its new and improved paradigm. And in the
meantime, those needing the old codebase can add a dependency on
net.imagej:imagej-ops to retain full backwards compatibility.
Migrate imglib2-ui to its own repository

See: https://github.com/imglib/imglib2-ui
Migrate imglib2-realtransform to its own repository

See: https://github.com/imglib/imglib2-realtransform
Remove algorithms components

As discussed at the October 2014 ImgLib2 hackathon in Madison, they have
migrated to their own Git repositories:

* https://github.com/imglib/imglib2-algorithms
* https://github.com/imglib/imglib2-algorithms-gpl
Remove imglib2-meta component

It migrated into imagej-common. Source at:

https://github.com/imagej/imagej-common

As discussed at the October 2014 ImgLib2 hackathon in Madison, the
imglib2-meta component is being merged into imagej-common, because:

* It simplifies the dependency hierarchy of ImageJ2-based projects.
* It will facilitate simplification of the relevant class hierachies,
  particularly net.imglib2.meta.ImgPlus vs. net.imagej.Dataset.