Add revised DoG detection implementation to algorithms-core.
added (and used) ${jama.version} property in imglib pom.
Merge branch 'master' into dog
removed generics from binaryops erode and dilate
Bump to pom-scijava 1.82

Signed-off-by: Jenkins <jenkins@dev.loci.wisc.edu>
Bump to pom-scijava 1.83

Signed-off-by: Jenkins <jenkins@dev.loci.wisc.edu>
Add some accessor API
ImgPlus: add a ctor that takes a CalibratedAxis...

Previously it was too difficult to create an ImgPlus linked to an
existing list of CalibratedAxis objects. The new constructor makes
this straightforward.
ImgPlus: copy the axes in the ImgPlusMetadata ctor

Previously, only the axis types, calibration scales and units were
cloned from the given ImgPlusMetadata. The proper behavior is to
clone the entire list of axes from it (using CalibratedAxes#copy)
as the new ImgPlus's axes.
ImgPlusTest: refactor instance field to local var
ImgPlusTest: use a better test method name
ImgPlusTest: add a test for the copy() method
PolynomialAxis: remove coefficient count limit

Firstly, it may be desirable to first create the axis before
programmatically adding a variable number of coefficients which are not
not known in advance.

Secondly, technically a polynomial axis can have less than three
coefficients. I think this check was just in place because LinearAxis
serves the same purpose if there are only one or two coefficients.
AbstractCalibratedAxis: override equals & hashCode

This allows CalibratedAxis instances to be compared for equality
in a non-trivial way. Equality is defined by the types, units and
particular equations of the axes all being equal.
Test each axis implementation's copy() method
DefaultLinearAxisTest: refactor field to local var
IdentityAxisTest: use slightly better test name
Define a coordinate transform function
DefaultLinearAxis: remove unnecessary parentheses
DefaultUnitService: improve parsing error handling

It is bad to catch Exception because that will catch many other types of
exceptions including all RuntimeExceptions. It is also bad to completely
eat the exception with no way of knowing what it was.

We remedy both problems by:

A) Emitting the exception as an error using the LogService; and
B) Centrally catching each type of checked exception individually.