Allow maven version number value as content module version number

The reloadonstartup functionality currently looks at a build number value in order to determine whether to reload the initialize items or not. This requires the developer to manually increase the buildnumber when they don't want to trigger a reload every time a checkin is made to the project. If we would allow the version number to be a maven version number then this would allow a reload strategy based on project version boundaries.