Cannot make local changes. Dispite previous comments This is still a
frustrating issue!
I have the following project structure:
── webserverbase
├── config
│ ├── config.go
├── example
│ ├── go.mod // Mod file 1
│ ├── go.sum
│ ├── webserver.go
├── exec
│ ├── exec.go
│ └── exec_test.go
├── go.mod // Mod file 2
├── go.sum
Mod File 1:
module webserver.go
go 1.13
require github.com/mygit/webserverbase v0.1.0-alpha // indirect
replace github.com/mygit/webserverbase/config v0.1.0-alpha => ../config
Mod File 2:
module github.com/mygit/webserverbase
go 1.13
At $GOPATH/pkg \mod\github.com\mygit\web!server!base@v0.1.0-alpha\ The
whole project source branch
In the examples dir I can:
go install webserver.go
I get an exe in:
C:\Users\user\go\bin
If I change webserverbase\config\config.go NOTHING CHANGES! Dispite the
replace in the go.mod file.
I need to make local changes to config before pushing to git. What am I
dooing wrong!
I even introduced a syntax error in to config.go. It is IGNORED!
Please Please help. I cannot see where I am going wrong! It should not be
this hard!
Stuart
On Monday, 23 September 2019 16:25:30 UTC+1, Stuart Davies wrote:
>
> Hi.
>
>
> I have been using GO for about a year and I love the language and ideas
> behind the language. I am also a Java developer for many years, I switched
> from Delphi to Java 1, the new and exciting language from Sun (a bit like
> GO is now from Google).
>
>
>
> In Java we have Maven and Gradle (sorry Ant) to make dependency hell more
> manageable so I understand the need for modules in Go. I have just
> installed GO 1.13 and thought I would convert an existing 'pet' project to
> use modules. It did NOT go well!
>
>
>
> What I need is a dummies guide to the GO module so I can build good,
> reliable, standards compliant GO applications.
>
>
>
> I needs to explain the new terminology in the context of a module, like
> 'vendor'. Not just a one liner, I NEED to understand!
>
>
>
> I know how to use Google but the quality of the articles I have read on
> this subject is minimal and just brushes the surface.
>
>
>
> If I have a reasonably large and complex (pet) project with local packages
> in it. I like to split my project in to small units with 'namespaces' to
> keep it manageable. These are NOT reusable components until I decide they
> qualify and publish on Github.
>
> - Why MUST I import them as if they are from github and then 'replace'
> them, and if I don’t 'MUST' then you have failed to explain this feature
> to
> me!
> - My local packages are part of my application. They are, I agree
> still 'dependencies' but they are not 'DEPENDENCIES' that I need (or even
> want) to import from a repository. They are part of my project.
> - What if I do not want to host my project on a GIT repo (Shock
> horror!).
> - Why do all imports start with github.com. Is that a requirement,
> what is the rational for this.
> - How does a 'import' resolve its 'reference'.
> - Should I add the go.mod and go.sum files to my repository or should
> the developer who cloned my project have to do a go mod init (bummer!).
>
> *Can someone please explain, properly!*
>
> We must have Modules and Repositories (like Maven Central) for the
> 'Enterprise' to manage dependencies but what about 'keep it simple' for the
> rest of us (and for that matter more mature enterprise developers like
> myself).
>
>
>
> Please help me get this understood. This is the sort of thing that can
> raise a language above the rest and I would really like that to happen. Go
> is brilliant…
>
>
>
> Regards
>
>
>
> Stuart
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/359f7342-dc9c-48f8-8608-cb52a301752d%40googlegroups.com.
