Github user johnmccabe commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/1170#issuecomment-176288949
@ahgittin its a bit messy to pull the -dist artifact in from a directory
outside of the Vagrantfile directory, hence the copy step. I changed
INSTALL_FROM_LOCAL_DIST to take a path to the file to deploy (ie to your .m2
example earlier) and added the steps to copy it to the ruby Vagrantfile -
what's messy is detecting *when* to run this, it should only occur on an `up`,
or `provision` is specified, I don't see a way to get at that context from the
Vagrantfile however - so you end up copying for all vagrant commands (up,
destroy etc).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
