[GitHub] incubator-eagle pull request: EAGLE-125 add LICENSE in eagle-exter...

2016-01-13 Thread qinzhaokun 
GitHub user qinzhaokun opened a pull request:

https://github.com/apache/incubator-eagle/pull/63

EAGLE-125 add LICENSE in eagle-external

https://issues.apache.org/jira/browse/EAGLE-125

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinzhaokun/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/63.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #63


commit d393e27dbd1ae0e2c70eeec3e952195fbdfa1943
Author: qinzhaokun 
Date:   2016-01-13T08:11:16Z

EAGLE-125 add LICENSE in eagle-external




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15095799#comment-15095799
 ] 

ASF GitHub Bot commented on EAGLE-125:
--

GitHub user qinzhaokun opened a pull request:

https://github.com/apache/incubator-eagle/pull/63

EAGLE-125 add LICENSE in eagle-external

https://issues.apache.org/jira/browse/EAGLE-125

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinzhaokun/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/63.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #63


commit d393e27dbd1ae0e2c70eeec3e952195fbdfa1943
Author: qinzhaokun 
Date:   2016-01-13T08:11:16Z

EAGLE-125 add LICENSE in eagle-external




> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-125 add LICENSE in eagle-exter...

2016-01-13 Thread haoch 
Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/63#issuecomment-171297690
  
@qinzhaokun looks good for me, will merge and thanks for the contribution.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-125 add LICENSE in eagle-exter...

2016-01-13 Thread haoch 
Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/63#issuecomment-171297597
  
LGTM 

:+1: 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-125 add LICENSE in eagle-exter...

2016-01-13 Thread qinzhaokun 
Github user qinzhaokun commented on the pull request:

https://github.com/apache/incubator-eagle/pull/63#issuecomment-171265697
  
Sorry to make that mistake. Thank @pmujumdar , I have updated AUTHOR.md, 
@haoch can you help to review this PR?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096212#comment-15096212
 ] 

ASF GitHub Bot commented on EAGLE-125:
--

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/63#issuecomment-171297690
  
@qinzhaokun looks good for me, will merge and thanks for the contribution.


> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-125 add LICENSE in eagle-exter...

2016-01-13 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/63


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096222#comment-15096222
 ] 

ASF GitHub Bot commented on EAGLE-125:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/63


> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096062#comment-15096062
 ] 

ASF GitHub Bot commented on EAGLE-125:
--

Github user qinzhaokun commented on the pull request:

https://github.com/apache/incubator-eagle/pull/63#issuecomment-171265697
  
Sorry to make that mistake. Thank @pmujumdar , I have updated AUTHOR.md, 
@haoch can you help to review this PR?


> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread Hao Chen (JIRA) 

 [ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen closed EAGLE-125.
--

> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: Is "Sensitive file info" in HBase always up-to-date?

2016-01-13 Thread Daniel Zhou 
I prefer incremental updates.
"Wipe off everything and insert everything" is quite straightforward, but it is 
not scalable when the metadata is increasing.

My idea about "incremental updates":
As eagle can get messages from "hdfs", we can also filter all the 
"delete/modify" message to update metadata in HBase.

Regards,
Daniel
  

-Original Message-
From: Edward Zhang [mailto:yonzhang2...@apache.org] 
Sent: Tuesday, January 12, 2016 11:40 PM
To: dev@eagle.incubator.apache.org
Subject: Re: Is "Sensitive file info" in HBase always up-to-date?

Hi Daniel,

Eagle does not have maintain this consistency. As sensitivity metadata normally 
comes from external tools by scanning file system, this consistency can be 
enforced by external tools. But looks we need think about metadata update 
algorithm. Do we wipe off everything and insert everything or just do 
incremental updates?

Thanks
Edward

On Tue, Jan 12, 2016 at 7:01 PM, Daniel Zhou 
wrote:

> Just a short question:
>
> Now in HBase  eagle have stored the info of sensitive files, including 
> the file name and sensitive type defined by user.
> If  these sensitive files in hadoop got deleted, how would this "delete"
> action affect the info stored in the HBase ? would their record  in HBase
> also get deleted?   (let's say I didn't create policies for these files)
>
> Regards,
> Daniel
>

Re: suggestion: add field "threshold" to current "fileSensitivity structure" in Eagle

2016-01-13 Thread Zhang, Edward (GDI Hadoop) 
Yes, looks we need a schema abstraction which can represent any
sensitivity information.
sensitivityType and numOfOccurrences are just two common fields of the
whole sensitivity information.

For hdfs, the sensitivity information also includes filedir, while for
hive, the sensitivity information includes hiveResource, which could be
database, table, column etc.

Thanks
Edward

On 1/13/16, 0:35, "Prasad Mujumdar"  wrote:

> The number of occurrences is certainly a good idea.
> For the HDFS and any future data sources which don't have native schema,
>how do we handle these fields which are defined in an external system ?
>Are
>you proposing to add a schema abstraction as well ?
>
>thanks
>Prasad
>
>
>On Tue, Jan 12, 2016 at 11:49 PM, Edward Zhang 
>wrote:
>
>> Hi Daniel,
>>
>> That is great idea to add more meaningful fields into sensitivity
>>metadata,
>> you can go ahead to design/add that.
>>
>> Only one concern is : how do we name this field generally? and what
>>else is
>> possible for future. numOfOccurrences could be a good name, for hdfs or
>> hive, the occurrence is defined differently.
>>
>> Thanks
>> Edward
>>
>> On Mon, Jan 11, 2016 at 7:38 PM, Daniel Zhou 
>> wrote:
>>
>> > Hi all,
>> >
>> > Recently I am working on a project to automatically fetch the
>>metadata of
>> > sensitive info stored in DB and then create eagle policy. I am
>>wondering
>> if
>> > we can add a field called "threshold" to current "fileSensitivity
>> > structure" in eagle so that we can create a policy with more details.
>> >
>> > Our company's product "DgSecure" can discover all the sensitive
>>elements
>> > within every file in hadoop  automatically,  so we have many details
>>of
>> > these sensitive information. With these information, we can make the
>> policy
>> > more precisely.  For example, I want to create a policy based on two
>> > parameters, one is  "sensitivity type", the other is called
>>"threshold".
>> > Only when the total number of that particular sensitive type element
>> > reaches or exceeds "threshold" can the alerts be triggered.
>> >
>> > So the trigger condition could be something like this:
>> >  if (sensitiveType == "MailAddress" && NumberOfSensData
>> > >=threshodl) .
>> >
>> > I think this condition makes more sense than just tagging a file with
>>a
>> > sensitive type.
>> >
>> > Please let me know if you have any opinions or suggestions. :)
>> >
>> > Thanks!
>> > Daniel
>> >
>>

Re: [Welcome] New Contributors in Apache Eagle

2016-01-13 Thread Edward Zhang 
Welcome Murali and Zhaokun. I know you have done a lot :-)

thanks
Edward

On Wed, Jan 13, 2016 at 10:27 PM, arunkarthick m 
wrote:

> Welcome Murali and Zhaokun Qin. Thanks for your contributions.
>
> Looking forward to be working with you.
>
> Regards,
> Arun
>
> On Wed, Jan 13, 2016 at 9:29 PM, Michael Wu  wrote:
>
> > It's my pleasure, team. Thanks for your words. 
> >
> > On Wed, Jan 13, 2016 at 7:04 PM, Hao Chen  wrote:
> >
> > > Welcome Zhaokun Qin as well, who has made great contributions for eagle
> > > docker image.
> > >
> > > Regards,
> > > Hao
> > >
> > > On Wed, Jan 13, 2016 at 4:17 PM, Prasad Mujumdar 
> > > wrote:
> > >
> > > >   Thanks!
> > > > Looking forward to work with the community to make better
> > contributions!
> > > >
> > > > thanks
> > > > Prasad
> > > >
> > > >
> > > > On Tue, Jan 12, 2016 at 3:45 PM, Arun Manoharan <
> > > arunmanoha...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Everyone,
> > > > >
> > > > > In the last 2 months we have had some increasing participation and
> > > active
> > > > > discussions from the community on various topics.
> > > > >
> > > > > I would like to thank Prasad Mujumdar, Ralph Su, Michael Wu, Daniel
> > > Zhou
> > > > > for their contributions to the project.
> > > > >
> > > > > Thanks,
> > > > > Arun
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Arun Karthick
> 201-850-9399
>

Re: [Welcome] New Contributors in Apache Eagle

2016-01-13 Thread arunkarthick m 
Welcome Murali and Zhaokun Qin. Thanks for your contributions.

Looking forward to be working with you.

Regards,
Arun

On Wed, Jan 13, 2016 at 9:29 PM, Michael Wu  wrote:

> It's my pleasure, team. Thanks for your words. 
>
> On Wed, Jan 13, 2016 at 7:04 PM, Hao Chen  wrote:
>
> > Welcome Zhaokun Qin as well, who has made great contributions for eagle
> > docker image.
> >
> > Regards,
> > Hao
> >
> > On Wed, Jan 13, 2016 at 4:17 PM, Prasad Mujumdar 
> > wrote:
> >
> > >   Thanks!
> > > Looking forward to work with the community to make better
> contributions!
> > >
> > > thanks
> > > Prasad
> > >
> > >
> > > On Tue, Jan 12, 2016 at 3:45 PM, Arun Manoharan <
> > arunmanoha...@apache.org>
> > > wrote:
> > >
> > > > Hi Everyone,
> > > >
> > > > In the last 2 months we have had some increasing participation and
> > active
> > > > discussions from the community on various topics.
> > > >
> > > > I would like to thank Prasad Mujumdar, Ralph Su, Michael Wu, Daniel
> > Zhou
> > > > for their contributions to the project.
> > > >
> > > > Thanks,
> > > > Arun
> > > >
> > >
> >
>



-- 
Arun Karthick
201-850-9399

RE: [Welcome] New Contributors in Apache Eagle

2016-01-13 Thread Krishna, Murali(AWF) 
Thank you Arun and Edward :)
Looking forward to contribute more.

- Murali Krishna

-Original Message-
From: Edward Zhang [mailto:yonzhang2...@apache.org] 
Sent: Thursday, January 14, 2016 12:06 PM
To: dev@eagle.incubator.apache.org
Subject: Re: [Welcome] New Contributors in Apache Eagle

Welcome Murali and Zhaokun. I know you have done a lot :-)

thanks
Edward

On Wed, Jan 13, 2016 at 10:27 PM, arunkarthick m 
wrote:

> Welcome Murali and Zhaokun Qin. Thanks for your contributions.
>
> Looking forward to be working with you.
>
> Regards,
> Arun
>
> On Wed, Jan 13, 2016 at 9:29 PM, Michael Wu  wrote:
>
> > It's my pleasure, team. Thanks for your words. 
> >
> > On Wed, Jan 13, 2016 at 7:04 PM, Hao Chen  wrote:
> >
> > > Welcome Zhaokun Qin as well, who has made great contributions for 
> > > eagle docker image.
> > >
> > > Regards,
> > > Hao
> > >
> > > On Wed, Jan 13, 2016 at 4:17 PM, Prasad Mujumdar 
> > > 
> > > wrote:
> > >
> > > >   Thanks!
> > > > Looking forward to work with the community to make better
> > contributions!
> > > >
> > > > thanks
> > > > Prasad
> > > >
> > > >
> > > > On Tue, Jan 12, 2016 at 3:45 PM, Arun Manoharan <
> > > arunmanoha...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Everyone,
> > > > >
> > > > > In the last 2 months we have had some increasing participation 
> > > > > and
> > > active
> > > > > discussions from the community on various topics.
> > > > >
> > > > > I would like to thank Prasad Mujumdar, Ralph Su, Michael Wu, 
> > > > > Daniel
> > > Zhou
> > > > > for their contributions to the project.
> > > > >
> > > > > Thanks,
> > > > > Arun
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Arun Karthick
> 201-850-9399
>

EAGLE-95 design

2016-01-13 Thread Krishna, Murali(AWF) 
Hi Team,

Would like your input/review on the design proposed for 
EAGLE-95 available in this 
Wiki.
The objective is to mark down policies that are identified as invalid and be 
skipped during the start of a topology.

We can use SiddhiCompiler.parseQuery() to validate the policy mentioned in the 
alertdef expression.
The above can be done at the AlertExecutor class while creating evaluator 
objects, on methods - init(), onPolicyCreated() and onPolicyChanged()
The same can be updated in the alertdef table for the corresponding policy by 
adding columns - markdown and markdownReason. This can be shown in the UI for 
the user to know what is wrong with the policy.

During the preparation of the PolicyEvaluator map available in AlertExecutor, 
we can add/modify/delete entries for policy IDs based on the output of the 
parseQuery().


-  Murali Krishna

Re: [Welcome] New Contributors in Apache Eagle

2016-01-13 Thread Michael Wu 
It's my pleasure, team. Thanks for your words. 

On Wed, Jan 13, 2016 at 7:04 PM, Hao Chen  wrote:

> Welcome Zhaokun Qin as well, who has made great contributions for eagle
> docker image.
>
> Regards,
> Hao
>
> On Wed, Jan 13, 2016 at 4:17 PM, Prasad Mujumdar 
> wrote:
>
> >   Thanks!
> > Looking forward to work with the community to make better contributions!
> >
> > thanks
> > Prasad
> >
> >
> > On Tue, Jan 12, 2016 at 3:45 PM, Arun Manoharan <
> arunmanoha...@apache.org>
> > wrote:
> >
> > > Hi Everyone,
> > >
> > > In the last 2 months we have had some increasing participation and
> active
> > > discussions from the community on various topics.
> > >
> > > I would like to thank Prasad Mujumdar, Ralph Su, Michael Wu, Daniel
> Zhou
> > > for their contributions to the project.
> > >
> > > Thanks,
> > > Arun
> > >
> >
>

Re: suggestion: add field "threshold" to current "fileSensitivity structure" in Eagle

2016-01-13 Thread Zhang, Edward (GDI Hadoop) 
problem with this approach is that if our data structure is nested in a
json, it is hard to be used for policy creation. Today looks Siddhi CEP
engine only supports flat structure unless we customize some comparison
function for this json field.

Thanks
Edward

On 1/13/16, 14:13, "Daniel Zhou"  wrote:

>How about we define some common fields and then add a String field to
>save a JSON file, which can be used to save any special fields defined in
>external system. Eagle only needs to take care of the common fields and
>external system can save any data they want in that JSON string field.
>
>Regards,
>Daniel
>
>-Original Message-
>From: Zhang, Edward (GDI Hadoop) [mailto:yonzh...@ebay.com]
>Sent: Wednesday, January 13, 2016 1:18 PM
>To: dev@eagle.incubator.apache.org
>Subject: Re: suggestion: add field "threshold" to current
>"fileSensitivity structure" in Eagle
>
>Yes, looks we need a schema abstraction which can represent any
>sensitivity information.
>sensitivityType and numOfOccurrences are just two common fields of the
>whole sensitivity information.
>
>For hdfs, the sensitivity information also includes filedir, while for
>hive, the sensitivity information includes hiveResource, which could be
>database, table, column etc.
>
>Thanks
>Edward
>
>On 1/13/16, 0:35, "Prasad Mujumdar"  wrote:
>
>> The number of occurrences is certainly a good idea.
>> For the HDFS and any future data sources which don't have native
>>schema, how do we handle these fields which are defined in an external
>>system ?
>>Are
>>you proposing to add a schema abstraction as well ?
>>
>>thanks
>>Prasad
>>
>>
>>On Tue, Jan 12, 2016 at 11:49 PM, Edward Zhang
>>
>>wrote:
>>
>>> Hi Daniel,
>>>
>>> That is great idea to add more meaningful fields into sensitivity
>>>metadata,  you can go ahead to design/add that.
>>>
>>> Only one concern is : how do we name this field generally? and what
>>>else is  possible for future. numOfOccurrences could be a good name,
>>>for hdfs or  hive, the occurrence is defined differently.
>>>
>>> Thanks
>>> Edward
>>>
>>> On Mon, Jan 11, 2016 at 7:38 PM, Daniel Zhou
>>> 
>>> wrote:
>>>
>>> > Hi all,
>>> >
>>> > Recently I am working on a project to automatically fetch the
>>>metadata of
>>> > sensitive info stored in DB and then create eagle policy. I am
>>>wondering
>>> if
>>> > we can add a field called "threshold" to current "fileSensitivity
>>> > structure" in eagle so that we can create a policy with more details.
>>> >
>>> > Our company's product "DgSecure" can discover all the sensitive
>>>elements
>>> > within every file in hadoop  automatically,  so we have many
>>> > details
>>>of
>>> > these sensitive information. With these information, we can make
>>> > the
>>> policy
>>> > more precisely.  For example, I want to create a policy based on
>>> > two parameters, one is  "sensitivity type", the other is called
>>>"threshold".
>>> > Only when the total number of that particular sensitive type
>>> > element reaches or exceeds "threshold" can the alerts be triggered.
>>> >
>>> > So the trigger condition could be something like this:
>>> >  if (sensitiveType == "MailAddress" && NumberOfSensData
>>> > >=threshodl) .
>>> >
>>> > I think this condition makes more sense than just tagging a file
>>> > with
>>>a
>>> > sensitive type.
>>> >
>>> > Please let me know if you have any opinions or suggestions. :)
>>> >
>>> > Thanks!
>>> > Daniel
>>> >
>>>
>

[jira] [Created] (EAGLE-126) enable basic support for eagle RDBMS storage

2016-01-13 Thread Edward Zhang (JIRA) 
Edward Zhang created EAGLE-126:
--

 Summary: enable basic support for eagle RDBMS storage
 Key: EAGLE-126
 URL: https://issues.apache.org/jira/browse/EAGLE-126
 Project: Eagle
  Issue Type: New Feature
Affects Versions: 0.3.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: 0.3.0


Eagle supports RDBMS as storage besides hbase, but we need clean up some tests 
and fix some bugs before we try it in production.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-125) Add LICENSE in eagle external

2016-01-13 Thread Hao Chen (JIRA) 

 [ 
https://issues.apache.org/jira/browse/EAGLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen resolved EAGLE-125.

Resolution: Resolved

> Add LICENSE in eagle external
> -
>
> Key: EAGLE-125
> URL: https://issues.apache.org/jira/browse/EAGLE-125
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
>
> When use: mvn clean install -DskipTests to compile source code, There are 
> ERRORs due to LICENSE missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)