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
goBin is not hornor #13
Comments
am I right that you trying to redefine the output directory for build result? if so then it is defined in |
best practice not to change project/build/directory since it impacts other plugins in the build lifecycle |
exactly, but mvn-golang plugin changes the lifecycle totally because it is not java based one, thus plugins which are sensetive to java lifecycle and environment have to be moved into another module of same project and they will be processed in right java lifecycle |
this not about java code, it can be other plugins. For example my msi-maven-plugin also uses that global config too :-) |
standard lifecycle processors will not be working because just will not find needed content in golang project and will not be able to install and deploy anything, the only way is to separate plugins in different modules of the same project imho like as in multimodule example |
your last comment addressing my install/deploy issue? or about goBin. If user are not allowed to alter goBin may be best to remove it from plugin's configuration. Would you accept PR? :-) |
goBin just allows to define $GOBIN during build process, I had complain for the value in the request, so I made that it can be disabled for working process just with |
i think i can use resultFolder. you may want to update goBin to refer user to resultFolder settings |
the default value for |
Go: 1.7.1
mvn: 3.3.9
this plugin: 2.1.2 (ie latest)
I am trying to configure goBin to use ${project.build.directory}/bin
the outputs always go to ${project.build.directory}
The text was updated successfully, but these errors were encountered: