Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/459
Pulled down the latest version of this branch:
```
Downloading:
https://repo.maven.apache.org/maven2/org/apache/metron/metron-test-utilities/0.4.0/metron-test-utilities-0.4.0.jar
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Metron ............................................. FAILURE [
16.984 s]
[INFO] metron-analytics ................................... SKIPPED
[INFO] metron-maas-common ................................. SKIPPED
[INFO] metron-platform .................................... SKIPPED
[INFO] metron-test-utilities .............................. SKIPPED
[INFO] metron-integration-test ............................ SKIPPED
[INFO] metron-maas-service ................................ SKIPPED
[INFO] metron-common ...................................... SKIPPED
[INFO] metron-statistics .................................. SKIPPED
[INFO] metron-writer ...................................... SKIPPED
[INFO] metron-storm-kafka ................................. SKIPPED
[INFO] metron-hbase ....................................... SKIPPED
[INFO] metron-profiler-common ............................. SKIPPED
[INFO] metron-profiler-client ............................. SKIPPED
[INFO] metron-profiler .................................... SKIPPED
[INFO] metron-enrichment .................................. SKIPPED
[INFO] metron-indexing .................................... SKIPPED
[INFO] metron-solr ........................................ SKIPPED
[INFO] metron-pcap ........................................ SKIPPED
[INFO] metron-parsers ..................................... SKIPPED
[INFO] metron-pcap-backend ................................ SKIPPED
[INFO] metron-data-management ............................. SKIPPED
[INFO] metron-api ......................................... SKIPPED
[INFO] metron-management .................................. SKIPPED
[INFO] elasticsearch-shaded ............................... SKIPPED
[INFO] metron-elasticsearch ............................... SKIPPED
[INFO] metron-deployment .................................. SKIPPED
[INFO] Metron Ambari Management Pack ...................... SKIPPED
[INFO] metron-docker ...................................... SKIPPED
[INFO] metron-interface ................................... SKIPPED
[INFO] metron-config ...................................... SKIPPED
[INFO] metron-rest-client ................................. SKIPPED
[INFO] metron-rest ........................................ SKIPPED
[INFO] site-book .......................................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 17.458 s
[INFO] Finished at: 2017-05-02T10:02:36-06:00
[INFO] Final Memory: 44M/333M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project
Metron: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin:
Failed to execute goal on project metron-integration-test: Could not resolve
dependencies for project org.apache.metron:metron-integration-test:jar:0.4.0:
Could not find artifact org.apache.metron:metron-test-utilities:jar:0.4.0 in
clojars.org (http://clojars.org/repo) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
```
---
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.
---
