Parameterize mvn-veresion consistently 82/78082/1
authorThanh Ha <thanh.ha@linuxfoundation.org>
Fri, 23 Nov 2018 09:36:17 +0000 (17:36 +0800)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Fri, 23 Nov 2018 09:36:19 +0000 (17:36 +0800)
For some reason we are hardcoding in some places and using variables
in others. Consistently name all the variable instances to mvn-version
so that a single parameter mvn-version can be passed to set the
version.

Change-Id: Ic689e6754299e7bff6e7a5f83f57a9d9caea64f9
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
jjb/autorelease/autorelease-templates.yaml

index e483b3d2ba7db069743d4b9ba5533a01c1aee35b..50a23191e5080fa7f000a29415e6238eb7447310 100644 (file)
@@ -79,7 +79,7 @@
 
     parameters:
       - maven-exec:
-          maven-version: 'mvn35'
+          maven-version: '{mvn-version}'
       - lf-infra-parameters:
           project: '{project}'
           stream: '{stream}'
       # to enable building in a single maven reactor afterwards.
       - autorelease-fix-relative-paths
       - maven-target:
-          maven-version: 'mvn35'
+          maven-version: '{mvn-version}'
           pom: 'pom.xml'
           goals: |
               clean deploy
       - autorelease-get-integration-test-variables
       - autorelease-maven-sources:
           opendaylight-infra-mvn-opts: '{opendaylight-infra-mvn-opts}'
-          maven-version: 'mvn35'
+          maven-version: '{mvn-version}'
           settings: 'autorelease-settings'
           global-settings: 'global-settings'
       - shell: |