Trying out dozer for data binding
Added Dozer mapping between ProposedConceptResponse and ProposedConceptDto
more Dozer mappings - getProposalById_simpleProposal_shouldBindToDto passes now
Concept DataType to String Dozer converted was wrongly removed - brought it back in
Brought back in ConceptConverter in the mapping - but not sure whether it is really needed.
Missing try catch after conversion to Dozer - thus failing to return an failure status for invalid requests
Merge pull request #44 from patrickdiligent/dozer

Dozer
- Added spring integration for Dozer. Added service for dozer mapper.
- move the data mapping tests from dictionary manager controller test (unit test) to Cpm Mapper Service (integration test)  since the mapping requires spring context to be initialized
- add the dozer dependency to pom too (till we officially migrate to gradle)
update dozer for proposal controller to use spring service bean
Switching to constructor DI for easier testing
Converting to unit test with mocking for improved speed & checking
Reordering and separating tests into 3 different categories for each of the RESTful apis
Ceola, Moiz & Dave: Setup test & mappings for DTO->Entity on proposal save
Added tests & mappings for review side
Setup datatype to be one way
Added test & mappings for serialising a submission into a dto
Module split: Created 'conceptpropose' and 'conceptreview' sub projects; moved code into conceptpropose; renamed packages
fix directory paths so that grunt tasks work
move grunt files and package.json files to conceptpropose and conceptreview sub-projects
move review bits from conceptpropose to conceptreview (and clone other bits for the moment)