Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-30 Thread Billie Rinaldi
It's optional. Here are the instructions for publishing maven artifacts: http://www.apache.org/dev/publishing-maven-artifacts.html On Wed, Mar 30, 2016 at 8:52 AM, Casey Stella wrote: > Taylor, I noticed that you have uploading to repository.apache.org in the > template for

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-30 Thread Casey Stella
Taylor, I noticed that you have uploading to repository.apache.org in the template for the release vote. First, is that strictly required? Second, if so, are there instructions? I'm having some problems uploading the bundle created by the mvn repository plugin to a staging repo due to a missing

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Casey Stella
Ok, I created a PR with the changes mentioned in this thread: - Removed extraneous LICENSE files and COPYING files - Fixed the verbiage for the cisco contribution in the LICENSE file - Added link to the license files for the 3rd party

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Casey Stella
We are currently generating the site with jekyll and infra has something setup that will pull the site from git. Casey On Tue, Mar 29, 2016 at 7:55 PM, P. Taylor Goetz wrote: > Yeah, I think that should cover it. > > In terms of licensing issues with the website code, I

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Billie Rinaldi
On Tue, Mar 29, 2016 at 12:46 PM, Casey Stella wrote: > Regarding the use of effective_tld_names.dat, it is in use currently in the > Whois enrichment adapter (for stripping top level domains from domains), > but that adapter is not turned on in the tech preview. That being

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread P. Taylor Goetz
Those .dat files are under the Mozilla Public License v. 2.0. So to comply you can point to the files (the way I pointed out earlier in the thread) in the LICENSE file and add the following text: This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread P. Taylor Goetz
For minified JavaScript or even things like images that can’t have license headers, you can put the license information in your LICENSE file. Here’s a snippet from Storm’s LICENSE file for an image: - For statistic image:

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Casey Stella
Regarding the use of effective_tld_names.dat, it is in use currently in the Whois enrichment adapter (for stripping top level domains from domains), but that adapter is not turned on in the tech preview. That being said, it's likely we will want to use that file in the future. Since this is a

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Casey Stella
Thanks Taylor, Regarding the bundled dependencies. We are bundling minified versions of those javascript dependencies, so they're not coming along with the license files or anything. I can place the license files in a directory next to them, but we're not capturing the source distribution, is

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread P. Taylor Goetz
Looking at the actual release I found the following: There are multiple LICENSE files: $ find ./ -name LICENSE .//LICENSE .//metron-streaming/LICENSE .//metron-ui/LICENSE There’s also ./bro-plugin-kafka/COPYING You should probably remove the extra LICENSE files and keep the top level one. The

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread P. Taylor Goetz
a > > Thanks, > James > > From: "P. Taylor Goetz" <ptgo...@gmail.com<mailto:ptgo...@gmail.com>> > Reply-To: > <dev@metron.incubator.apache.org<mailto:dev@metron.incubator.apache.org>> > Date: Monday, March 28, 2016 at 5:17 PM > To: <dev

Re: [RESULT][VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread Casey Stella
ok, thanks for tracing it down! Debugging our build instructions is almost more important than debugging the build. ;) On Tue, Mar 29, 2016 at 8:59 AM, larry mccay wrote: > I see what is happening... > > When I build using the provided command at root, the first attempt

Re: [RESULT][VOTE] Release of Metron_0.1BETA_rc5

2016-03-29 Thread larry mccay
I see what is happening... When I build using the provided command at root, the first attempt fails with some permission denied error. Then when I retry it is left in the streaming directory because the && cd .. didn't get executed due to the failure. So, the rat execution was happening from

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-28 Thread James Sirota
28, 2016 at 5:17 PM >To: <dev@metron.incubator.apache.org<mailto:dev@metron.incubator.apache.org>> >Subject: Re: [VOTE] Release of Metron_0.1BETA_rc5 > >My apologies for not weighing in sooner. > >Github: >https://github.com/apache/incubator-metron/releases/tag

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-24 Thread Hakkı Hakan Akansel
All components works well, however if you restart the single-node local machine, all services are stopped and you should start these services. On Thu, Mar 24, 2016 at 5:56 PM, Nick Allen wrote: > +1 (non-binding) > > Fully functioning in Amazon EC2 and local

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-23 Thread James Sirota
Small correction on the validation instructions. For Step 1, execute the mvn command from incubator-metron/ and not incubator-metron/metron-streaming/ Thanks, James On 3/22/16, 3:56 PM, "James Sirota" wrote: > >A tag has been created for Metron_0.1BETA_RC5 >

Re: [VOTE] Release of Metron_0.1BETA_rc5

2016-03-23 Thread Casey Stella
+1, non-binding On Tue, Mar 22, 2016 at 6:56 PM, James Sirota wrote: > > A tag has been created for Metron_0.1BETA_RC5 > > Github: > https://github.com/apache/incubator-metron/releases/tag/Metron_0.1BETA_rc5 > Apache: >