Preparing for maven staging releases

Adding version.properties file to contain release_variable property.
Adding maven staging plugin to pom file.

Change-Id: I310a27a75ca62408f253a69d461718cbad0c6815
Signed-off-by: Patrick Brady <pb071s@att.com>

diff --git a/pom.xml b/pom.xml
index 1c5673e..cfb0a08 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -502,6 +502,18 @@
     <build>
         <pluginManagement>
             <plugins>
+                <!--maven staging plugin-->
+                <plugin>
+                    <groupId>org.sonatype.plugins</groupId>
+                    <artifactId>nexus-staging-maven-plugin</artifactId>
+                    <version>1.6.7</version>
+                    <extensions>true</extensions>
+                    <configuration>
+                        <nexusUrl>${nexusproxy}</nexusUrl>
+                        <stagingProfileId>176c31dfe190a</stagingProfileId>
+                        <serverId>ecomp-staging</serverId>
+                    </configuration>
+                </plugin>
                 <!-- Define the site plugin to generate documentation -->
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>

diff --git a/version.properties b/version.properties
new file mode 100644 (file)
index 0000000..d8dc243
--- /dev/null
+++ b/version.properties
@@ -0,0 +1,13 @@
+###########################################################
+# Versioning variables
+# Note that these variables cannot be structured (e.g. : version.release or version.snapshot etc... )
+# because they are used in Jenkins, whose plug-in doesn't support
+
+release_name=1
+sprint_number=0
+feature_revision=0
+
+base_version=${release_name}.${sprint_number}.${feature_revision}
+
+release_version=${base_version}
+snapshot_version=${base_version}-SNAPSHOT