GeographicCoordinate 4.1.1
-
Fixed incorrect exception messages. When supplying an invalid value to the Latitude(double) or Longitude(double) constructors, the resulting exception message said that the lower bound for valid values was 0. This is incorrect when using floating-point notation; valid values can be negative. The actual validation logic was correct - this was only an issue with the literal text of the error message.
-
Moved Eclipse project files to
.eclipse_project_filesso that my project setup isn't forced on everyone. See.eclipse_project_files/README.txtfor more information. -
Updated JUnit tests