Thanks for all the quick and clear responses.
Seems like I was unnecessarily complicating the workflow. The single go.mod
structure worked.
Go community is awesome !!!
On Saturday, March 9, 2019 at 2:54:25 PM UTC+5:30, Paul Jolly wrote:
>
> Modules can contains multiple packages
> (https://go
Modules can contains multiple packages
(https://golang.org/cmd/go/#hdr-Modules__module_versions__and_more).
So all the packages listed in the tree above can be contained within a
single module (go.mod) defined at the top most level.
To take a random example of this, take a look at
https://github.
not required, the service must be able to import bll/* and possibly other
sub packages.
On Saturday, March 9, 2019 at 2:31:48 AM UTC+5:30, Paul Jolly wrote:
>
> (full disclosure, I wrote
>
> https://github.com/go-modules-by-example/index/blob/master/009_submodules/README.md)
>
>
>
> Quick firs
Use only one go.mod, at the root level of the project.
--
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,
(full disclosure, I wrote
https://github.com/go-modules-by-example/index/blob/master/009_submodules/README.md)
Quick first question: are you absolutely sure you need multiple modules?
https://github.com/golang/go/wiki/Modules#faqs--multi-module-repositories
On Fri, 8 Mar 2019 at 20:49, Abhishek
Trying to make modules work for the below project structure
.
├── bll
│ ├── billing
│ │ ├── details.go
│ │ └── go.mod
│ ├── complaint
│ │ ├── details.go
│ │ └── go.mod
│ └── task
│ ├── details.go
│ └── go.mod
├── go.mod
└── services
├── billing
│ ├── go.
