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

"mvn deploy" doesn't attempt to deploy an artifact to the maven repository #2

Closed
roxspring opened this issue May 24, 2016 · 3 comments
Assignees
Milestone

Comments

@roxspring
Copy link

Running mvn deploy I fully expect to have the results of my maven build deployed into our Artifactory but don't get that result with the golang extension present. To be honest, when running mvn install I full expect to get the binary in my ~/.m2/repository/ too but that doesn't happen here either. I understand that its' not necessarily straight forward when trying to harmonize the verbs of the two build systems but these seem pretty major departures from the maven tradition!

@raydac
Copy link
Owner

raydac commented May 24, 2016

mvn deploy wraps go install command, it would be interesting to make deploying also into maven repository but I have not any idea what to deploy in the case, to deploy executable result file? but such artefact can't be used as dependency in future

@raydac raydac added this to the 2.1.0 milestone May 27, 2016
@raydac raydac self-assigned this May 27, 2016
raydac added a commit that referenced this issue May 27, 2016
…ved the get operation to select branch and tag
@raydac
Copy link
Owner

raydac commented May 27, 2016

since 2.1.0 it will be creating artifact in local repository for mvn install

@raydac raydac closed this as completed May 27, 2016
@roxspring
Copy link
Author

Cool - thanks!

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