Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go build fails with go1.16.4 because of missing go.mod file #650

Closed
de-jcup opened this issue Jun 1, 2021 · 1 comment · Fixed by #953
Closed

go build fails with go1.16.4 because of missing go.mod file #650

de-jcup opened this issue Jun 1, 2021 · 1 comment · Fixed by #953
Assignees
Labels
bug Something isn't working build client
Milestone

Comments

@de-jcup
Copy link
Member

de-jcup commented Jun 1, 2021

Situation

Executing integration tests with

./gradlew integrationtest

on my local machine fails with:

> Task :sechub-cli:buildGo FAILED
Build go:Start building package 'daimler.com/sechub'
>building:platform/linux-386
no required module provides package daimler.com/sechub: go.mod file not found in current directory or any parent directory; see 'go help modules'
Go build failed because of an error

Checking version:

> $ go version
go version go1.16.4 linux/amd64

Wanted

Build shall work with newer go versions as well - e.g. for security reasons (compiler output

Solutions

There a two possible options IMHO:

A) integrate adequate go.mod file which works for 1.15.x and also 1.16.x
B) Make a workaround via setting GOPATH ala
GOPATH="~/go:./sechub-cli" inside the gradle build file

@de-jcup de-jcup added bug Something isn't working build client labels Jun 1, 2021
@de-jcup
Copy link
Member Author

de-jcup commented Jun 1, 2021

Some interesting links:

@sven-dmlr sven-dmlr added this to the Client 0.27.0 milestone Sep 10, 2021
@sven-dmlr sven-dmlr self-assigned this Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working build client
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants