It could be fine to start a wiki page to list the tools and ide 
(not)ready for modules with the linked issues.

In https://github.com/golang/go/wiki/Modules or a new page ?

On 29-08-2018, Paul Jolly wrote:
> --00000000000050127c057491b176
> Content-Type: text/plain; charset="UTF-8"
>
> Please see https://github.com/golang/gddo/issues/567
>
> On Tue, 28 Aug 2018, 18:59 Justin Israel, <[email protected]> wrote:
>
>> I've been trying out converting some of our internal projects to go 1.11
>> using modules instead of glide. We have a build system that provides the
>> ability to generate html docs via "godoc" and I am wondering if godoc has
>> been made "module-aware" in go 1.11?
>>
>> My particular project is using the migration approach of setting "v3" at
>> in the go.mod, and in all import paths within the project. But it seems
>> godoc is not happy about this:
>>
>> godoc -links=0 -html domain.com/group/project/v3/lib/foo
>>
>> 2018/08/29 11:52:12 error while importing build package: cannot find package 
>> "domain.com/group/project/v3/lib/foo" in any of:
>>         /path/to/go/1.11.0/src/domain.com/group/project/v3/lib/foo (from 
>> $GOROOT)
>>         /usr/home/justin/src/go/src/domain.com/group/project/v3/lib/foo 
>> (from $GOPATH)
>> 2018/08/29 11:52:12 cannot find package "." in:
>>         /src/domain.com/group/project/v3/lib/foo
>>
>>
>> It seems to only care about the filesystem structure and not the module 
>> import path naming?
>>
>>
>> Justin
>>
>>
>> --
>> 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 [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>


-- 
William

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to