[GitHub] incubator-eagle pull request #249: Eagle 352 make necessary changes for prep...

[anyway1021]

GitHub user anyway1021 opened a pull request:

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

Eagle 352 make necessary changes for preparing 0.4.0 release candidate 2



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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-352

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

https://github.com/apache/incubator-eagle/pull/249.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 #249


commit a2f93f44181cb6265861f95eb9c7374d4b332753
Author: anyway1021 
Date:   2016-07-01T05:04:38Z

add LICENSE to eagle-docs/images/asf_logo.svg

commit 4886b6f4bab20a944a1d9760ba0c67b1674f6357
Author: anyway1021 
Date:   2016-07-01T05:09:42Z

change the first line of CHANGELOG.txt, adding apache branding content

commit 3b31dd8fe9ba0d138bc0eda88b2b63231a9354a3
Author: anyway1021 
Date:   2016-07-01T05:10:58Z

highlight the requirement of NPM for building eagle in README.md

commit 0709be4e0fd9cf6e50535d6ec227c10a20164652
Author: anyway1021 
Date:   2016-07-01T05:11:53Z

add LICENSE to eagle-webservice/src/main/webapp/README.md

commit d2db3d638716164b172c17bfad2c8d8c831c9268
Author: anyway1021 
Date:   2016-07-05T14:47:17Z

move apache-rat-plugin's configuration tag out of executions tag to make it 
effective

commit 3acf497014081472437ed77ce53d6bb377a89b76
Author: anyway1021 
Date:   2016-07-05T15:05:17Z

modify CHANGELOG.txt for v0.4, merging the CHANGELOGs of v0.3 and v0.3.1 at 
the bottom




---
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.
---

[PR Review Request] PR#249 has been opened for the changes made for preparing 0.4.0 rc2, please help review it

[Michael Wu]

Hi guys,

I've made changes according to the findings of 0.4.0 rc1, and opened PR #249
. Please DO help review
it as soon as possible.

BTW, can anyone suggest how many works we have to do to solve "branding"
issue on eagle's site page? Do we plan to erase all of the branding issues
in 0.4.0 release? Thanks.

Michael

Re: [PR Review Request] PR#249 has been opened for the changes made for preparing 0.4.0 rc2, please help review it

[Edward Zhang]

Eagle site code is maintained separately in another github repo. It
contains all of changes for Eagle 0.4 except that we may need fix some of
branding issues. I will fix allo of them. Please let me know why 0.4 code
release has dependency on eagle site code?

Thanks
Edward

On Tue, Jul 5, 2016 at 8:14 AM, Michael Wu  wrote:

> Hi guys,
>
> I've made changes according to the findings of 0.4.0 rc1, and opened PR
> #249
> . Please DO help
> review
> it as soon as possible.
>
> BTW, can anyone suggest how many works we have to do to solve "branding"
> issue on eagle's site page? Do we plan to erase all of the branding issues
> in 0.4.0 release? Thanks.
>
> Michael
>

[GitHub] incubator-eagle issue #249: Eagle 352 make necessary changes for preparing 0...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/249
  
reviewed and merged.


---
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 #246: EAGLE-347. Replace remaining version numb...

[pkuwm]

Github user pkuwm closed the pull request at:

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


---
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 issue #246: EAGLE-347. Replace remaining version number "0.3...

[pkuwm]

Github user pkuwm commented on the issue:

https://github.com/apache/incubator-eagle/pull/246
  
Merged.


---
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-347) Replace "v0.3.0" to "v0.3.1" in eagle-topology-init.sh

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-347:
--

Github user pkuwm commented on the issue:

https://github.com/apache/incubator-eagle/pull/246
  
Merged.


> Replace "v0.3.0" to "v0.3.1" in eagle-topology-init.sh
> --
>
> Key: EAGLE-347
> URL: https://issues.apache.org/jira/browse/EAGLE-347
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.1
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.3.1
>
>
> We still have "v0.3.0" in eagle-topology-init.sh.  Should be changed to 
> "v0.3.1".



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

[jira] [Commented] (EAGLE-347) Replace "v0.3.0" to "v0.3.1" in eagle-topology-init.sh

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-347:
--

Github user pkuwm closed the pull request at:

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


> Replace "v0.3.0" to "v0.3.1" in eagle-topology-init.sh
> --
>
> Key: EAGLE-347
> URL: https://issues.apache.org/jira/browse/EAGLE-347
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.1
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.3.1
>
>
> We still have "v0.3.0" in eagle-topology-init.sh.  Should be changed to 
> "v0.3.1".



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

[GitHub] incubator-eagle pull request #250: Rebase code base

[RalphSu]

GitHub user RalphSu opened a pull request:

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

Rebase code base



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

$ git pull https://github.com/RalphSu/incubator-eagle develop

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

https://github.com/apache/incubator-eagle/pull/250.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 #250


commit 329711581d6cc7f8f9e73f3b91bc98246e9a8874
Author: Ralph, Su 
Date:   2016-07-05T12:14:20Z

migrate code




---
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.
---

Re: [PR Review Request] PR#249 has been opened for the changes made for preparing 0.4.0 rc2, please help review it

[Michael Wu]

@Edward,

No, it doesn't depend on the site code, I was just asking if we have to
solve the branding issue in 0.4 because I saw the email discussing about
it. Please don't care about it and continue the maintenance for site code,
I'll create RC2 as soon as possible. Thanks.

Michael

On Wed, Jul 6, 2016 at 4:49 AM, Edward Zhang 
wrote:

> Eagle site code is maintained separately in another github repo. It
> contains all of changes for Eagle 0.4 except that we may need fix some of
> branding issues. I will fix allo of them. Please let me know why 0.4 code
> release has dependency on eagle site code?
>
> Thanks
> Edward
>
> On Tue, Jul 5, 2016 at 8:14 AM, Michael Wu  wrote:
>
> > Hi guys,
> >
> > I've made changes according to the findings of 0.4.0 rc1, and opened PR
> > #249
> > . Please DO help
> > review
> > it as soon as possible.
> >
> > BTW, can anyone suggest how many works we have to do to solve "branding"
> > issue on eagle's site page? Do we plan to erase all of the branding
> issues
> > in 0.4.0 release? Thanks.
> >
> > Michael
> >
>

[GitHub] incubator-eagle pull request #249: Eagle 352 make necessary changes for prep...

[anyway1021]

Github user anyway1021 closed the pull request at:

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


---
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] [Closed] (EAGLE-352) Fix found issues on release-0.4.0-rc1 and create rc2

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-352.

Resolution: Done

> Fix found issues on release-0.4.0-rc1 and create rc2
> 
>
> Key: EAGLE-352
> URL: https://issues.apache.org/jira/browse/EAGLE-352
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> need to:
> 1. change the dir name inside the tar, 
> 2. modify release note head-line, 
> 3. highlight the building requirement of npm in README.md, 
> 4. add LICENSE to asf_logo.svg
> 5. solve branding issues



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

[GitHub] incubator-eagle issue #249: Eagle 352 make necessary changes for preparing 0...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/249
  
The change looks good, thanks @anyway1021 


---
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 issue #250: Rebase code base

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/250
  
The code sync should skip `pom.xml`


---
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 #250: Rebase code base

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/250#discussion_r69672601
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/pom.xml ---
@@ -10,14 +10,14 @@
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ~ See 
the 
License for the specific language governing permissions and ~ 
limitations 
under the License. -->
-http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
 

org.apache.eagle
-   eagle-alert
-   0.5.0-incubating-SNAPSHOT
-   ../pom.xml
+   alert-parent
+   0.0.1-SNAPSHOT
--- End diff --

:-1: fix such kinds of version changes.


---
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 #250: Rebase code base

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/250#discussion_r69672628
  
--- Diff: eagle-core/eagle-alert-parent/eagle-alert/alert-service/pom.xml 
---
@@ -0,0 +1,169 @@
+
+
+http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+   
+   alert-parent
+   org.apache.eagle
+   0.0.1-SNAPSHOT
+   
+   4.0.0
+
+   alert-service
+   Alert Service: Coordinator + Metadata
+   jar
+
+   
+   
+   org.apache.eagle
+   alert-coordinator
+   ${project.version}
+   
+   
+   org.slf4j
+   slf4j-log4j12
+   
+   
+   storm-core
+   org.apache.storm
+   
+   
+   
+   
+   org.apache.eagle
+   alert-metadata-service
+   ${project.version}
+   
+   
+   org.slf4j
+   slf4j-log4j12
+   
+   
+   storm-core
+   org.apache.storm
+   
+   
+   
+
+   
+   com.sun.jersey
+   jersey-json
+   
+   
+   
+   io.dropwizard
+   dropwizard-core
+   
+   
+   org.slf4j
+   slf4j-log4j12
+   
+   
+   
+   
+   io.dropwizard
+   dropwizard-jersey
+   
+   
+   org.slf4j
+   slf4j-log4j12
+   
+   
+   
+   
+   io.swagger
+   swagger-jersey-jaxrs
+   compile
+   
+   
+   com.sun.jersey
+   *
+   
+   
+   
+   
+   
+   
+   
+   org.eclipse.jetty
+   jetty-maven-plugin
+   9.2.11.v20150529
--- End diff --

Resolve hard-coded pom version.


---
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 #250: Rebase code base

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/250#discussion_r69672680
  
--- Diff: eagle-core/eagle-alert-parent/eagle-alert/pom.xml ---
@@ -61,12 +154,17 @@

org.apache.curator
curator-framework
-   ${curator.version}
+   ${curator-framework.version}
+   
+   
+   org.apache.curator
+   curator-test
+   ${curator.test.version}


org.apache.curator
curator-recipes
-   ${curator.version}
+   ${curator-framework.version}
--- End diff --

Resolve duplicated dependencies version.


---
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 #250: Rebase code base

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/250#discussion_r69672722
  
--- Diff: eagle-core/eagle-alert-parent/eagle-alert/pom.xml ---
@@ -107,7 +205,7 @@

org.slf4j
slf4j-log4j12
-   ${slf4j-log4j12.version}
+   ${slf4j-log4j12.veresion}
--- End diff --

Bad word `slf4j-log4j12.veresion`


---
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 issue #250: Rebase code base

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/250
  
There may be some version problem, please clean up following apache eagle's 
naming standard.


---
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.
---

[VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 2)

[Michael Wu]

Hi all,

This is a release vote for Apache Eagle, version 0.4.0-incubating, release
candidate 2.

Highlighted changes in this release are as the following:
  * JBDC Metadata Storage Extension
  * Topology management in remote mode including start/stop/status
operations
  * Auditlogparser for MapR's audit log
  * Oozie auditlog integration for Oozie security monitoring
  * Add applicaiton "maprFSAuditLog"
  * Refactor bin/eagle-sandbox-starter.sh to make it easier to use

Thanks to everyone who has contributed to this release.

Here's the release note:
https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4

The artifacts to be voted on are located at:
https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc2/

The commit to be voted upon:
*https://github.com/apache/incubator-eagle/commit/23d3ca604a37ccb89d7a95e5c75cfba651673b2a
*

Release tag is:
*https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc2
*

Release artifacts are signed with the following key:
http://people.apache.org/keys/committer/mw.asc

The hashes of the artifacts are as follows:
apache-eagle-0.4.0-incubating-src-rc2.tar.gz.md5:
0a78ed6c36ba57194f6721a8d6bae6f4
apache-eagle-0.4.0-incubating-src-rc2.tar.gz.sha1:
f59b3d7d894181eb2019bb55f4cf6079a47339eb

Please vote on releasing this package as: Apache Eagle 0.4.0-incubating.

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PPMC votes are cast.

[ ] +1 Release this Apache Eagle 0.4.0-incubating Release Candidate 2.

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Thanks.

Michael