Randomly Hangs Forever #144
Comments
Nope, it's the first time I see this problem. Some questions:
My advice:
|
gradle is 4.1 gogradle is 0.7 most recent OS is redhat linux 6.8 yes there is a scala project and go project go |
Also what is this packagePath. I don't understand what its purpose is
|
Like what does this happen
|
Well... I highly recommend you to take a look at the doc, which tells you what is Anyway, is the project structure that you pasted root project or just a sub project? Please see java and go mixed example as an example. Please let me know if there's anything not clear. |
does one app execuable = one project? |
A go project can produce mutiple app executable, but don't mix scala code and go code in one project (i.e. apply both golang and scala plugin in one project). |
yes so my top level build.gradle is actually empty and there are two top level folders one is named go and the other is named scala |
ok, I guess I know what bothers you. Where does |
so if I navigate into the go directory i have three folders bin (pre-gogradle) , src (pre-gogradle) , vendor (this was generated by gogradle) , also I have build.gradle
then i go into src directory |
The project structure you pasted previously is such a mess... Actually, your structure should be:
And in your
However, you really need to read https://golang.org/doc/code.html first. |
And try to make it work in single project, then integrate it with your scala project. |
So I read more about go and made this project https://github.com/jeb2239/practice_go . Some things I don't understand is why does there need to a separated directory for each main.go file . Also I still don't understand how this system can be used to build multiple binaries even when I explicitly have 2 go build commands it only makes one of the binaries. Thank you so much for your help! |
First question, that behavior is determined by go build command. There should be one Second question, for the moment, you need to use the following
The reason is only one command is allowed in |
why do we need .gogradle and the symlink - this seems to be a gogradle specific requirement. |
The symlink is not necessary. If you confrom to golang's standard structure and have everything under As for |
Also why does gogradle resolve dependencies from the latest commit even when a specific commit is requested.
|
I'm also getting problems like this after running The progress indicator locks at
Versions:
Seems like there are no more logs after This problem also exists in 0.6.5 but not 0.5.4. |
@jeb2239 The reason why the latest commit is resolved is that it's someone's transitive dependency. "Resolve" means fetching the metadata and resolving conflict. In this case, you specify a commit, but transitive dependencies includes another version (latest commit), so both will be "resolved" and the latest one will be discarded (See here for conflict resolution strategy). And you can use Could you take a look at the final version installed into |
@minid33 Does this occur every time? Would you like to try the latest I can't find any issue in the log you pasted, so it would be great if you could give me a sample to reproduce it. |
Without failure @blindpirate, I first encountered this in latest This is a copy of our build.gradle after running
|
|
I read the whole log and I guess this is what you're looking for...
This is a golang install using This is when |
looks like resolveIfNecessary() or something further down the chain needs to either accept the Full logs are here: |
Not really. Gogradle will try to access all path in
So that's definitely not the problem. However, after examining you log, it hangs in
Thanks a lot. |
the There are no test dependencies in this build.gradle file. There never have been, I think this is the default behaviour of changed a |
Thanks for the response. That's weird, do you have Now could you please remove all I really want a sample which I can run in my machine to reproduce it if possible. |
./gradlew go:build
Starting a Gradle Daemon (subsequent builds will be faster)
It also make no progress. Has this happened to anyone?
The text was updated successfully, but these errors were encountered: