Switch over to using github.com/go-jira/jira, from gopkg.in

thor/jira

mirror of https://github.com/Threnklyn/jira.git synced 2026-05-18 20:23:28 +02:00

There should be no reason to use gopkg.in versioned imports now that
we're using go modules. I think, IANAE.

gopkg.in kind of gets in the way of modules, as it only pulls over
tagged releases from github.com -- this then means that you need to use
go modules 'replace' syntax in the go.mod to use a non-versioned commit
or branch. This is feasible, but kind of ugly.

go modules defaults to pulling the latest version, so the default
behavior is the same as when pulling go-jira.v1 from gopkg.in.

This commit is contained in:

Mike Pountney

2019-09-08 19:06:52 -07:00

parent 71aaa88b13

commit 27f57b2bbe

59 changed files with 123 additions and 121 deletions

									
										go.mod
									
		+1
		-1
	
												View File
												
				@@ -1,4 +1,4 @@

				module gopkg.in/Netflix-Skunkworks/go-jira.v1

				module github.com/go-jira/jira

				go 1.12