I recommend letting the go tool handle this. Leave the dependency out of the go.mod file entirely. Run go build as normal, and it will automatically determine the version strings for the dependencies and insert them into your go.mod for you.
On Wed, Nov 14, 2018 at 5:43 AM Russel Winder <rus...@winder.org.uk> wrote: > I am giving the module system in Go 1.11.2 a whirl to get projects out of > the > GOPATH environment. The dependencies include ones that have no tagged > versions > in the Git repositories. The documentation implies that I can use "dev" as > the > version number in the go.mod file for this situation. However, this just > causes a compilation failure: > > invalid module version "dev": unknown revision dev > > I am hoping I am just misreading something about the documentation! > > -- > Russel. > =========================================== > Dr Russel Winder t: +44 20 7585 2200 > 41 Buckmaster Road m: +44 7770 465 077 > London SW11 1EN, UK w: www.russel.org.uk > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
