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

correctly process stderr output of golang tools if no errors #55

Closed
daqingshu opened this issue Jan 21, 2019 · 4 comments
Closed

correctly process stderr output of golang tools if no errors #55

daqingshu opened this issue Jan 21, 2019 · 4 comments
Assignees
Milestone

Comments

@daqingshu
Copy link

when use go 1.11.x
config GO111MODULE = on
use go.mod file
when mvn compile, the console output like this:

[ERROR] ---------Exec.Err---------
[ERROR] go: finding github.com/modern-go/reflect2 v1.0.1
[ERROR] go: finding github.com/json-iterator/go v1.1.5

I think this just the go common output, not ERROR
want get help, thanks

@raydac raydac self-assigned this Jan 21, 2019
@raydac
Copy link
Owner

raydac commented Jan 21, 2019

unfortunately I can do nothing in the case because everything works correct
I don't know why but Golang team exactly uses err stream to print such messages

if !QuietLookup {
			fmt.Fprintf(os.Stderr, "go: finding %s %s\n", r.path, rev)
		}

and my wrapper just shows what it gets from error stream

@raydac
Copy link
Owner

raydac commented Jan 21, 2019

I have created issue report for golang team

@raydac raydac changed the title work with go 1.11 got error log output correctly process stderr output of golang tools if no errors Jan 21, 2019
@raydac
Copy link
Owner

raydac commented Jan 21, 2019

I will make some improvements in plugin to log their messages because looks like that they just use error stream to log auxiliary info

@raydac raydac added this to the 2.2.1 milestone Jan 21, 2019
@daqingshu
Copy link
Author

I will make some improvements in plugin to log their messages because looks like that they just use error stream to log auxiliary info

thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants