Use https url as staging repo target
[releng/builder.git] / jjb / autorelease / include-raw-autorelease-maven-deploy.sh
index 96f0da1a4ad1d5a5b9ce645be96a2f07eea9a6ed..e9d1d465a05c451c9f6bf87c58ce7c4608505a46 100644 (file)
@@ -9,15 +9,6 @@
 # http://www.eclipse.org/legal/epl-v10.html
 ##############################################################################
 
-# Job will pass in a variable ${DATESTAMP} if this variable is false than we
-# we are likely releasing a release candidate. We should skip closing the
-# Nexus staging repository so that we can sign the artifacts.
-SKIP_STAGING_CLOSE=false
-if [ "${DATESTAMP}" == "false" ]
-then
-    SKIP_STAGING_CLOSE=true
-fi
-
 # Assuming that mvn deploy created the hide/from/pom/files/stage directory.
 cd hide/from/pom/files
 mkdir -p m2repo/org/opendaylight/
@@ -39,9 +30,8 @@ rsync -avz --exclude 'maven-metadata*' \
            "stage/org/opendaylight/integration" m2repo/org/opendaylight/
 
 mvn org.sonatype.plugins:nexus-staging-maven-plugin:1.6.2:deploy-staged-repository \
-    -DskipStagingRepositoryClose=${SKIP_STAGING_CLOSE} \
     -DrepositoryDirectory="`pwd`/m2repo" \
-    -DnexusUrl=http://nexus.opendaylight.org/ \
+    -DnexusUrl=https://nexus.opendaylight.org/ \
     -DstagingProfileId="425e43800fea70" \
     -DserverId="opendaylight.staging" \
     -s $SETTINGS_FILE \