summaryrefslogtreecommitdiffstats
path: root/dblib/provider/pom.xml
diff options
context:
space:
mode:
authorDan Timoney <dtimoney@att.com>2017-08-30 16:22:00 -0400
committerDan Timoney <dtimoney@att.com>2017-08-30 17:00:32 -0400
commitba02fc8ee8afa868dda1ca6f11d3dfa293ad4cf3 (patch)
tree5a4a8382933b84c3e318c11e076cb82cbfc9c906 /dblib/provider/pom.xml
parent9972ac595d679375014ad2ae31cd08618ac37e50 (diff)
Roll version to rule out staging issue
Behavior observed in the odlsli docker container suggests that it might be picking up an old build of 0.1.0-SNAPSHOT version of sli/core. We have observed this problem before due to issues with the Nexus staging plugin. This change bumps the version of sli/core to 0.1.1-SNAPSHOT and comments out the staging plugin from the sli/core pom.xml to make sure that the current build is picked up. There will be a corresponding change in ccsdk/distribution to change which version of sli/core is used in the odlsli container Change-Id: Ie3c2b4ff66191748df14240a69a7d461fc0d4639 Issue-ID: CCSDK-69 Signed-off-by: Dan Timoney <dtimoney@att.com>
Diffstat (limited to 'dblib/provider/pom.xml')
-rwxr-xr-xdblib/provider/pom.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/dblib/provider/pom.xml b/dblib/provider/pom.xml
index 579ab40e..1f9a5d47 100755
--- a/dblib/provider/pom.xml
+++ b/dblib/provider/pom.xml
@@ -4,10 +4,10 @@
<parent>
<groupId>org.onap.ccsdk.sli.core</groupId>
<artifactId>dblib</artifactId>
- <version>0.1.0-SNAPSHOT</version>
+ <version>0.1.1-SNAPSHOT</version>
</parent>
<artifactId>dblib-provider</artifactId>
- <version>0.1.0-SNAPSHOT</version>
+ <version>0.1.1-SNAPSHOT</version>
<packaging>bundle</packaging>
<name>DBLIB Adaptor - Provider</name>
<url>http://maven.apache.org</url>