Issue #42: Initial hackings to separate filter outcomes from
requirements.
Issue #42: Made an explicit ComponentRequirement. Collapsed Outcome and
FilterOutcome.
Fixed header
Merge branch 'master' into issue42
Deleted references to DataTypeFamily
Issue #14: Added missing @Initialize annotation
Issue #14: Added icon to UniqueKeyCheckAnalyzer
Issue #42: Fixed XML reading and writing of new requirement types.
Fixed lazy/eager loading of filteroutcomes
Issue #42: Fixed issue in handling requirement copies while
immutabilizing an AnalysisJob
Issue #42: Added InputRow to ComponentRequirement's interface to enable
implementations that does row-content based decisions
Merge pull request #43 from datacleaner/issue42

Fix made requirement-and-outcome separation (Issue42)
Renamed getOutcomes to getFilterOutcomes()
Added unittest to assert equality of different type filteroutcomes
Added unittest for asserting equality of different type filteroutcomes
Issue #42: Fixed eager loading of ComponentRequirements in
AnalyzerJobBuilder
[maven-release-plugin] prepare release AnalyzerBeans-1.0-RC3
[maven-release-plugin] prepare for next development iteration
Updated sprint-mock -> spring-test
Merge pull request #1 from datacleaner/master

Get latest from AnalyzerBeans.