From 31e2cdd834c3be3d59bc23ee2c4eff7874d80159 Mon Sep 17 00:00:00 2001
From: Jakob Odersky <jakob@odersky.com>
Date: Fri, 24 Aug 2018 14:37:50 -0700
Subject: Upgrade sbt-settings to major version 2 (#201)

This will affect development workflow: instead of running `sbt
release` to tag and publish a new version, the release process is now
as follows:
1. Create a git tag on a revision that should be published. The tag
must be in the format `v[0-9].*`
2. Push the tag to GitHub `git push --tags`
3. CI will build that tag and publish the resulting binary to our
artifactory

Since the new sbt settings do not enable advanced or risky language
features globally anymore (such as higher kinds, reflective calls and
implicit conversions), the other changes in this PR either import
language features locally or refactor the code to avoid using them
entirely.
---
 .travis.yml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to '.travis.yml')

diff --git a/.travis.yml b/.travis.yml
index c31881d..7845eae 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -4,8 +4,9 @@ jdk:
   - oraclejdk8
 
 scala:
-  - 2.12.3
+  - 2.12.6
 
 script:
   - echo 'credentials += Credentials("Artifactory Realm", "drivergrp.jfrog.io", "sbt-publisher", sys.env("ARTIFACTORY_PASSWORD"))' > project/credentials.sbt
-  - "sbt clean +test"
+  - sbt clean +test
+  - if [[ "$TRAVIS_PULL_REQUEST" == "false" && "$TRAVIS_TAG" =~ ^v[0-9].* ]]; then sbt publish; fi
-- 
cgit v1.2.3