Non "-SNAPSHOT" versions still append timestamp to module.properties version.

[bmlong137]

Here is an example output of mvn initialize. You can see the version is 1.4.0, without a -SNAPSHOT on the end.

brian-long@alfresco-brian:~/Code/git/gitlab.alfresco.com/alfresco-distributed-objects/distributed-objects-repo$ mvn initialize
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Distributed Objects 1.4.0
[INFO] ------------------------------------------------------------------------
[WARNING] The metadata /home/brian-long/.m2/repository/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata-sonatype-public.xml is invalid: end tag name </HEAD> must be the same as start tag <META> from line 1 (position: START_TAG seen ...ache/maven/plugins/maven-deploy-plugin/maven-metadata.xml"></HEAD>... @1:381) 
[INFO] 
[INFO] --- alfresco-maven-plugin:2.1.1:set-version (default-set-version) @ distributed-objects-repo ---
[INFO] Added timestamp to version - 1.4.0.1510281212
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.024s
[INFO] Finished at: Wed Oct 28 12:12:56 EDT 2015
[INFO] Final Memory: 13M/303M
[INFO] ------------------------------------------------------------------------

The only way I can prevent the timestamp from appending is to set snapshotToTimestamp to false. However, this would need to be changed every time I generate non-snapshot POMs. Plus it seems illogical that I need to set snapshotToTimestamp to stop a timestamp on a non-snapshot.

This is happening in the SDK v1.1.1, v2.1.0, and v2.1.1.

[gravitonian]

Tracked by: https://issues.alfresco.com/jira/browse/DEVPLAT-452

[gravitonian]

Fixed