updated README.md file, updated imports to use gopkg.in, added Makefile

Author: jucardi

.gitignore

@@ -1,6 +1,5 @@
 # Binaries for programs and plugins
 *.exe
-*.exe~
 *.dll
 *.so
 *.dylib
@@ -11,6 +10,14 @@
 # Output of the go coverage tool, specifically when used with LiteIDE
 *.out
 
+# Project-local glide cache, RE: https://github.com/Masterminds/glide/issues/736
+.glide/
+
+# IDEs folders
 .idea/
 .vscode/
 
+test-artifacts/
+build
+tmp
+

Makefile

@@ -0,0 +1,36 @@
+all: format vet deps test build
+
+format:
+	@echo "formatting files..."
+	@go get golang.org/x/tools/cmd/goimports
+	@goimports -w -l .
+	@gofmt -s -w -l .
+
+vet:
+	@echo "vetting..."
+	@go vet ./...
+
+deps:
+	@echo "installing dependencies..."
+	@go get ./...
+
+test-deps:
+	@echo "installing test dependencies..."
+	@go get github.com/smartystreets/goconvey/convey
+	@go get gopkg.in/h2non/gock.v1
+	@go get github.com/stretchr/testify/assert
+	@go get github.com/axw/gocov/...
+	@go get github.com/AlekSi/gocov-xml
+	@go get gopkg.in/matm/v1/gocov-html
+
+test: test-deps
+	@echo "running test coverage..."
+	@mkdir -p test-artifacts/coverage
+	@gocov test ./... -v > test-artifacts/gocov.json
+	@cat test-artifacts/gocov.json | gocov report
+	@cat test-artifacts/gocov.json | gocov-xml > test-artifacts/coverage/coverage.xml
+	@cat test-artifacts/gocov.json | gocov-html > test-artifacts/coverage/coverage.html
+
+build: deps
+	@echo "building..."
+	@go build ./...

README.md

@@ -6,10 +6,18 @@ This library is does not actually provide a logger implementation but instead by
 
 ## Getting started
 
+To keep up to date with the most recent version:
+
 ```bash
 go get github.com/jucardi/go-logger-lib
 ```
 
+To get a specific version:
+
+```bash
+go get gopkg.in/jucardi/go-logger-lib.v1
+```
+
 ## What inspired me to create this simple library?
 
 Working on a go project that I wanted to make open source, I realized that it would make sense to be able to have a logger and log information based on the results of certain operations. Originally I started using `github.com/sirupsen/logrus` which is a very good Go logging library, but I didn't want the consumers of my project to be forced to use `logrus` if they were already using a different logger.

log/formatter_helpers.go

@@ -2,11 +2,12 @@ package log
 
 import (
 	"fmt"
-	"github.com/jucardi/go-iso8601"
-	"github.com/jucardi/go-streams/streams"
-	"github.com/jucardi/go-terminal-colors"
 	"strings"
 	"text/template"
+
+	"gopkg.in/jucardi/go-iso8601.v1"
+	"gopkg.in/jucardi/go-streams.v1/streams"
+	"gopkg.in/jucardi/go-terminal-colors.v1"
 )
 
 const (

log/formatter_themes.go

@@ -1,6 +1,6 @@
 package log
 
-import "github.com/jucardi/go-terminal-colors"
+import "gopkg.in/jucardi/go-terminal-colors.v1"
 
 // LevelColorScheme represents the terminal colors associated to the level parsing for each logging level.
 type LevelColorScheme map[Level][]fmtc.Color

log/level.go

@@ -2,7 +2,8 @@ package log
 
 import (
 	"fmt"
-	"github.com/jucardi/go-strings/stringx"
+
+	"gopkg.in/jucardi/go-strings.v1/stringx"
 )
 
 // These are the different logging levels. You can set the logging level to log

log/logger_logrus.go

@@ -2,6 +2,7 @@ package log
 
 import (
 	"bytes"
+
 	"github.com/sirupsen/logrus"
 )