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

    https://github.com/apache/incubator-metron/pull/544#discussion_r112961765
  
    --- 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 --
    
    So for "Quick Dev" it already had the "Build Metron" step.  All I did was 
change from 'package' to 'install'.  For "Full Dev" I just copied the same 
Build Step to the README as Quick Dev had.  What do I need to do to disentangle 
this PR from #538 ?  I'd rather not wait days to get such a simple fix into the 
README that ends up confusing a lot of users.


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