util: Use != 0 instead of == 2 for exit code assertions.
features: Add an extra assertion showing both children will come back.
all: Standardize the IvyDE project settings.
domain: Keep null primitives null in DataTransferObjectMapper

DataTransferObjectMapper was using toJdbcValue when it should have been using toDomainValue. This forced a tweak of aggregate generics to handle SmallInt. SmallInt is a good test because it has a different domain and JDBC type. Some extra code was needed to add toDomainValue to aggregates. I also needed to add toDomainValue(ResultSet, int) helper to ColumnExpression defined as toDomainValue(toJdbcValue(ResultSet, int)) so the generics type check correctly in DataTransferObjectMapper. I tried putting toDomainValue(toJdbcValue(ResultSet, int)) directly in DataTransferObjectMapper, but they were being called on ColumnExpression<?, ?> and Java's type capture did not recognize that the return value of toJdbcValue was the same type as the argument of toDomainValue.
Merge pull request #10 from mdietz198/master

domain: Keep null primitives null in DataTransferObjectMapper
migrations: Add support for custom one-to-many property names.
features: Integration test one-to-many custom names.
Merge branch 'master' into stable

* master:
  features: Integration test one-to-many custom names.
  migrations: Add support for custom one-to-many property names.
  domain: Keep null primitives null in DataTransferObjectMapper
  all: Standardize the IvyDE project settings.
  features: Add an extra assertion showing both children will come back.
  util: Use != 0 instead of == 2 for exit code assertions.