Just a heads up and hopefully not a distraction:

Per https://issues.apache.org/jira/browse/METRON-583, if we ever update to a 
never version of GROK, many of our existing rules are going to break.

I have a pull request out for this issue ( 
https://github.com/thekrakken/java-grok/pull/60 ) with them since November, but 
there has been no comment or movement on it.

On January 9, 2017 at 16:01:00, Michael Miklavcic ([email protected]) 
wrote:

This is a question primarily for the mentors.  

*Background*  
metron-common is currently depending on the openSOC github repo for hosting  
kraken artifacts. The original reason for this was that these jars are not  
hosted in Maven Central, and they were not reliably available in the Kraken  
repo. https://issues.apache.org/jira/browse/METRON-650 is tracking work  
around copying these artifacts to the Metron repo.  

Kraken source on openSOC - https://github.com/OpenSOC/kraken  
Krake maven repo on openSOC -  
https://github.com/OpenSOC/kraken/tree/mvn-repo  

*Ask*  
Create a new branch in incubator-metron to host any necessary maven  
artifacts. This branch would simply be incubator-metron/mvn-repo. This is  
similar to how we've hosted the asf-site.  

*Concerns/Questions*  

1. Can we host these jars/artifacts in this manner?  
2. Concerns regarding licensing?  
3. Do we need to also grab and host the source code?  

Reply via email to