[jira] [Updated] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-372: Affects Version/s: v0.5.0 Fix Version/s: v0.5.0 > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-373) Move Eagle document to Eagle source code control
Edward Zhang created EAGLE-373: -- Summary: Move Eagle document to Eagle source code control Key: EAGLE-373 URL: https://issues.apache.org/jira/browse/EAGLE-373 Project: Eagle Issue Type: Improvement Affects Versions: 0.5 Reporter: Edward Zhang Assignee: Edward Zhang Priority: Minor Fix For: 0.5 Today Eagle's document is maintained in https://github.com/eaglemonitoring/eaglemonitoring.github.io, it does not conform to Apache policy. We should move this into Apache git source control. The approach is to create a branch called document in https://github.com/apache/incubator-eagle/tree/document and put document into it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374047#comment-15374047 ] Edward Zhang commented on EAGLE-371: We tried with Eagle branch https://github.com/apache/incubator-eagle/tree/document long time ago, and will officially move all documents to this branch in Eagle 0.5. Use https://issues.apache.org/jira/browse/EAGLE-373 to track > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374066#comment-15374066 ] Julian Hyde commented on EAGLE-371: --- Thanks for logging this case, [~yonzhang2012]. Have you considered combining the web site with the documentation? You could put this into a directory of your source code (not a branch), or you could create a new git repo (hosted under apache.org, and mirrored under github.com/apache). > remove eagle-docs from develop branch > - > > Key: EAGLE-371 > URL: https://issues.apache.org/jira/browse/EAGLE-371 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Trivial > Fix For: 0.5 > > > eagle-docs will be maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't > need maintain duplicated documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-373) Move Eagle document to Eagle source code control
[ https://issues.apache.org/jira/browse/EAGLE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374076#comment-15374076 ] Julian Hyde commented on EAGLE-373: --- In my experience keeping docs on a branch is tricky. (It is impossible to fix the code AND update the doc in a single patch.) I find it easier to put them in a sub-directory of the source code. Or you could create a separate git repo. This issue must be fixed before Eagle graduates. > Move Eagle document to Eagle source code control > > > Key: EAGLE-373 > URL: https://issues.apache.org/jira/browse/EAGLE-373 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.5 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Minor > Fix For: 0.5 > > > Today Eagle's document is maintained in > https://github.com/eaglemonitoring/eaglemonitoring.github.io, it does not > conform to Apache policy. We should move this into Apache git source control. > The approach is to create a branch called document in > https://github.com/apache/incubator-eagle/tree/document and put document into > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)
+1 (binding) * Downloaded & built successfully with Hotspot JDK1.7 on OSX * Signature checked, md5, sha1 verified ( https://httpd.apache.org/dev/verification.html) * Apache rat:check passed (mvn apache-rat:check) * no jar files included. Thanks Edward On Mon, Jul 11, 2016 at 10:34 PM, Hao Chen wrote: > +1 (binding) > > Invalid JAR files issue reported in previous apache-eagle-0.4.0-incubating > rc2 have been resolved. > > * Downloaded & Built successfully on MacOSX 10.10.5 with Java > HotSpot 1.7.0_75. > * Verified signature > * Ran rat:check and passed > > - Hao > > On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi wrote: > > > +1 (non-binding) > > > > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X > > * Signature checked, md5, sha1 verified > > * Apache rat:check passed (mvn apache-rat:check) > > * Release matches tag. > > > > > > -Huizhi > > > > > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > > > > > Hi all, > > > > > > This is a release vote for Apache Eagle, version 0.4.0-incubating, > > release > > > candidate 3. > > > > > > 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.0 > > > < > > > https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0 > > >* > > > > > > The artifacts to be voted on are located at: > > > * > > > https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/ > > > < > > > https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/ > > >* > > > > > > The commit to be voted upon: > > > * > > > https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715 > > > < > > > https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715 > > >* > > > > > > Release tag is: > > > * > > > https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3 > > > < > > > https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3 > > >* > > > > > > 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-rc3.tar.gz.md5: > > > 5781048a2fc2b3dcfe5e30a09be86d25 > > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.sha1: > > > a98b565604b3921a4ea5c53e30479427b227e1e2 > > > > > > 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 3. > > > > > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > > > > > [ ] -1 Do not release this package because... > > > > > > > > > Thanks. > > > Michael > > > > >
[GitHub] incubator-eagle issue #265: EAGLE-372: Change AlertNotificationEntity#fields...
Github user zombieJ commented on the issue: https://github.com/apache/incubator-eagle/pull/265 LGTM --- 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-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374235#comment-15374235 ] ASF GitHub Bot commented on EAGLE-372: -- Github user zombieJ commented on the issue: https://github.com/apache/incubator-eagle/pull/265 LGTM > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #265: EAGLE-372: Change AlertNotificationEntity...
Github user qingwen220 closed the pull request at: https://github.com/apache/incubator-eagle/pull/265 --- 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-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374257#comment-15374257 ] ASF GitHub Bot commented on EAGLE-372: -- Github user qingwen220 closed the pull request at: https://github.com/apache/incubator-eagle/pull/265 > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)
+1 (binding) * Download & built successfully with Java HotSpot(TM) 64-Bit Server VM & java version "1.7.0_79" * All unit tests passed * License check passed * Jars files reported in apache-eagle-0.4.0-incubating rc2 have been resolved Best Regards, Qingwen Zhao | 赵晴雯 2016-07-13 9:03 GMT+08:00 Edward Zhang : > +1 (binding) > > * Downloaded & built successfully with Hotspot JDK1.7 on OSX > * Signature checked, md5, sha1 verified ( > https://httpd.apache.org/dev/verification.html) > * Apache rat:check passed (mvn apache-rat:check) > > * no jar files included. > > > Thanks > > Edward > > On Mon, Jul 11, 2016 at 10:34 PM, Hao Chen wrote: > > > +1 (binding) > > > > Invalid JAR files issue reported in previous > apache-eagle-0.4.0-incubating > > rc2 have been resolved. > > > > * Downloaded & Built successfully on MacOSX 10.10.5 with Java > > HotSpot 1.7.0_75. > > * Verified signature > > * Ran rat:check and passed > > > > - Hao > > > > On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi wrote: > > > > > +1 (non-binding) > > > > > > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X > > > * Signature checked, md5, sha1 verified > > > * Apache rat:check passed (mvn apache-rat:check) > > > * Release matches tag. > > > > > > > > > -Huizhi > > > > > > > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > > > > > > > Hi all, > > > > > > > > This is a release vote for Apache Eagle, version 0.4.0-incubating, > > > release > > > > candidate 3. > > > > > > > > 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.0 > > > > < > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0 > > > >* > > > > > > > > The artifacts to be voted on are located at: > > > > * > > > > > > https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/ > > > > < > > > > > > https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/ > > > >* > > > > > > > > The commit to be voted upon: > > > > * > > > > > > https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715 > > > > < > > > > > > https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715 > > > >* > > > > > > > > Release tag is: > > > > * > > > > > > https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3 > > > > < > > > > > > https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3 > > > >* > > > > > > > > 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-rc3.tar.gz.md5: > > > > 5781048a2fc2b3dcfe5e30a09be86d25 > > > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.sha1: > > > > a98b565604b3921a4ea5c53e30479427b227e1e2 > > > > > > > > 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 > 3. > > > > > > > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > > > > > > > [ ] -1 Do not release this package because... > > > > > > > > > > > > Thanks. > > > > Michael > > > > > > > > >
[jira] [Created] (EAGLE-374) sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their pom.xml
Michael Wu created EAGLE-374: Summary: sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their pom.xml Key: EAGLE-374 URL: https://issues.apache.org/jira/browse/EAGLE-374 Project: Eagle Issue Type: Bug Reporter: Michael Wu Assignee: Zhao, Qingwen Find below sub-modules lack of "relativePath" tag within "parent" tag in their own pom.xml, the tag should pointing to pom of respective parent. eagle-hadoop-queue eagle-jpm-entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-374) sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their pom.xml
[ https://issues.apache.org/jira/browse/EAGLE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-374: - Description: Find below sub-modules lack of "relativePath" tag within "parent" tag in their own pom.xml, the tag should pointing to pom of respective parent. eagle-hadoop-queue eagle-jpm-entity Error Message captured as: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.eagle:eagle-hadoop-queue:0.5.0-incubating-SNAPSHOT (/home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-jpm/eagle-hadoop-queue/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.apache.eagle:eagle-parent:pom:0.5.0-incubating-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 23, column 13 -> [Help 2] [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/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException was: Find below sub-modules lack of "relativePath" tag within "parent" tag in their own pom.xml, the tag should pointing to pom of respective parent. eagle-hadoop-queue eagle-jpm-entity > sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their > pom.xml > - > > Key: EAGLE-374 > URL: https://issues.apache.org/jira/browse/EAGLE-374 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Zhao, Qingwen > > Find below sub-modules lack of "relativePath" tag within "parent" tag in > their own pom.xml, the tag should pointing to pom of respective parent. > eagle-hadoop-queue > eagle-jpm-entity > Error Message captured as: > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.eagle:eagle-hadoop-queue:0.5.0-incubating-SNAPSHOT > (/home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-jpm/eagle-hadoop-queue/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact > org.apache.eagle:eagle-parent:pom:0.5.0-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 23, column 13 -> [Help > 2] > [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/ProjectBuildingException > [ERROR] [Help 2] > http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #266: EAGLE-374: Fix sub-modules of eagle-jpm l...
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/266 EAGLE-374: Fix sub-modules of eagle-jpm lack of relativePath tag https://issues.apache.org/jira/browse/EAGLE-374 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-374 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/266.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 #266 commit cf7c1fe47e8b5417677f870cb95350c81b467113 Author: Zhao, Qingwen Date: 2016-07-13T06:30:49Z Fix sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their 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. ---
[jira] [Commented] (EAGLE-374) sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their pom.xml
[ https://issues.apache.org/jira/browse/EAGLE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374457#comment-15374457 ] ASF GitHub Bot commented on EAGLE-374: -- GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/266 EAGLE-374: Fix sub-modules of eagle-jpm lack of relativePath tag https://issues.apache.org/jira/browse/EAGLE-374 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-374 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/266.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 #266 commit cf7c1fe47e8b5417677f870cb95350c81b467113 Author: Zhao, Qingwen Date: 2016-07-13T06:30:49Z Fix sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their pom.xml > sub-modules of eagle-jpm lack of relativePath tag pointing to parent in their > pom.xml > - > > Key: EAGLE-374 > URL: https://issues.apache.org/jira/browse/EAGLE-374 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Zhao, Qingwen > > Find below sub-modules lack of "relativePath" tag within "parent" tag in > their own pom.xml, the tag should pointing to pom of respective parent. > eagle-hadoop-queue > eagle-jpm-entity > Error Message captured as: > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.eagle:eagle-hadoop-queue:0.5.0-incubating-SNAPSHOT > (/home/jenkins/jenkins-slave/workspace/incubator-eagle-pr-reviewer/eagle-jpm/eagle-hadoop-queue/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact > org.apache.eagle:eagle-parent:pom:0.5.0-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 23, column 13 -> [Help > 2] > [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/ProjectBuildingException > [ERROR] [Help 2] > http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
