Preparing for maven staging releases

Changing version in version.properties file to 1.0.0.
Adding maven staging plugin to pom file.

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

diff --git a/pom.xml b/pom.xml
index c3f0aed..4ad304f 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -30,6 +30,18 @@
     </pluginRepositories>
     <build>
         <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>
             <!-- blackduck maven plugin -->
             <plugin>
                 <groupId>com.blackducksoftware.integration</groupId>
@@ -89,4 +101,4 @@
         <name>OpenECOMP</name>
     </organization>
     <version>1.0.0-SNAPSHOT</version>
-</project>
\ No newline at end of file
+</project>

diff --git a/version.properties b/version.properties
index 7092503..feea708 100644 (file)
--- a/version.properties
+++ b/version.properties
@@ -3,9 +3,9 @@
 # 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=0
+release_name=1
 sprint_number=0
-feature_revision=1
+feature_revision=0
 
 base_version=${release_name}.${sprint_number}.${feature_revision}