[GitHub] [metron] mmiklavc opened a new pull request #1398: METRON-2100: Update developer documentation for full dev management UI parser aggregation feature gap

[GitBox <gi...@apache.org>]

mmiklavc opened a new pull request #1398: METRON-2100: Update developer documentation for full dev management UI parser aggregation feature gap
URL: https://github.com/apache/metron/pull/1398
 
 
   https://issues.apache.org/jira/browse/METRON-2100
   
   This is a pure documentation update/clarification per the discussion here - https://lists.apache.org/thread.html/37e9727ae3053fb30dad86cca99f7c2bafea23bc4a5e36c6cf9cf10f@%3Cdev.metron.apache.org%3E. Testing in full dev should not be required.
   
   **Testing**
   
   Review the proposed documentation change. You can run through the site-book build if desired. I verified the change looks correct and that the added links to parser aggregation work as expected.
   
   ## Pull Request Checklist
   
   ### For all changes:
   - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
   - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
   - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
   
   
   ### For code changes:
   - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
   - [x] Have you included steps or a guide to how the change may be verified and tested manually?
   - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
     ```
     mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
     ```
   
   - n/a Have you written or updated unit tests and or integration tests to verify your changes?
   - n/a If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - n/a Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
   
   ### For documentation related changes:
   - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
   
     ```
     cd site-book
     mvn site
     ```
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services