Github user dlyle65535 commented on a diff in the pull request:

    https://github.com/apache/incubator-metron/pull/544#discussion_r112953201
  
    --- Diff: metron-deployment/vagrant/full-dev-platform/README.md ---
    @@ -24,35 +26,38 @@ Any platform that supports these tools is suitable, but 
the following instructio
     
     1. Install Homebrew by following the instructions at 
[Homebrew](http://brew.sh/).
     
    -2. Run the following command in a terminal to install all of the required 
tools.
    +1. Run the following command in a terminal to install all of the required 
tools.
     
    -  ```  
    -  brew cask install vagrant virtualbox java
    -  brew install maven git
    -  ```
    +    ```  
    +    brew cask install vagrant virtualbox java docker
    +    brew install maven git
    +    ```
     
    -3. Install Ansible by following the instructions 
[here](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip).
    +1. Install Ansible by following the instructions 
[here](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip).
     
     ### Deploy Metron
     
    -1. Install Vagrant Hostmanager.
    +1. Build Metron
     
    -  ```
    -  vagrant plugin install vagrant-hostmanager
    -  ```
    +    ```
    +    cd incubator-metron
    +    mvn clean install -DskipTests
    +    ```
     
    --- End diff --
    
    Yeah, completely understand. I don't like the idea of people running the 
build 2 times when it's absolutely not required. This is the 3rd PR we've 
introduced to "fix" the documentation without addressing the actual issue, 
which should be trivial- simply roll back METRON-827 which (I hope) is actually 
in work and will likely land before this does. @justinleet - is that a correct 
assumption?


---
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.
---

Reply via email to