[jira] [Commented] (EAGLE-394) Fix NPE bug while metadata inconsistent; Fix unit test

[ https://issues.apache.org/jira/browse/EAGLE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392925#comment-15392925 ] ASF GitHub Bot commented on EAGLE-394: -- Github user RalphSu commented on the issue:

[jira] [Commented] (EAGLE-394) Fix NPE bug while metadata inconsistent; Fix unit test

[ https://issues.apache.org/jira/browse/EAGLE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392926#comment-15392926 ] ASF GitHub Bot commented on EAGLE-394: -- GitHub user RalphSu reopened a pull request:

Re: Eagle build broken in github

I had the same issue with OpenJDK 1.8. But it works with Sun JDK 1.8. Bosco On 7/25/16, 5:37 PM, "Edward Zhang" wrote: Seems it is JDK issue? [INFO] Compiling 16 source files to

[GitHub] incubator-eagle pull request #273: EAGLE-394 : fix NPE and broken test

Github user RalphSu closed the pull request at: https://github.com/apache/incubator-eagle/pull/273 --- 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

[jira] [Commented] (EAGLE-394) Fix NPE bug while metadata inconsistent; Fix unit test

[ https://issues.apache.org/jira/browse/EAGLE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392924#comment-15392924 ] ASF GitHub Bot commented on EAGLE-394: -- Github user RalphSu closed the pull request at:

[jira] [Resolved] (EAGLE-394) Fix NPE bug while metadata inconsistent; Fix unit test

[ https://issues.apache.org/jira/browse/EAGLE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph resolved EAGLE-394. Resolution: Fixed > Fix NPE bug while metadata inconsistent; Fix unit test >

[GitHub] incubator-eagle pull request #273: EAGLE-394 : fix NPE and broken test

Github user RalphSu closed the pull request at: https://github.com/apache/incubator-eagle/pull/273 --- 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

Eagle build broken in github

Seems it is JDK issue? [INFO] Compiling 16 source files to /home/jenkins/jenkins-slave/workspace/incubator-eagle-main/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes at 1469439473203[ERROR] error: error while loading CharSequence, class file

Re: wish team prefect the doc

Thanks, Caoyu. #1 is a bug. That should be fixed. Have EAGLE-395 to track that. BTW: eagle docs are at https://github.com/eaglemonitoring/eaglemonitoring.github.io. You're welcome to send PR help us fix this. #2. I can see your screenshot. Can you tell us which version are you using? And

Re: Build failure in branch "develop"

I was mostly referring to a Docker container just for building. I know you have Docker for runtime. I have not tried that yet. Thanks Bosco On 7/25/16, 12:25 PM, "Edward Zhang" wrote: Thanks. Are you saying that you will build docker file for community to use?

Re: Build failure in branch "develop"

Thanks. Are you saying that you will build docker file for community to use? As far as I know current docker image is not fully tested and sometimes may not be stable as it contains HBase which is often down unexpectedly. Thanks Edward On Mon, Jul 25, 2016 at 12:21 PM, Don Bosco Durai

Re: Build failure in branch "develop"

Thanks. This worked. Additionally, I had to install node.js. Let me see if I can make the Dockerfile available in some form for others to use it (if needed). Bosco On 7/25/16, 1:28 AM, "Michael Wu" wrote: This issue has been fixed in develop branch. Michael

Re: Could u add jianxu1 into Eagle JIRA Assignee List

It looks as if you’re already on the “committers” and “developers” lists, and your name appears in the assignees drop down. Let me know if you still can’t assign to yourself. > On Jul 25, 2016, at 2:56 AM, Xu, Jian (SysDev) wrote: > > Eagle Dev > > I want to be eagle dev,

[jira] [Commented] (EAGLE-393) Fix UnitTest Error caused by streamDef.json and TestApplicationImpl

[ https://issues.apache.org/jira/browse/EAGLE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391668#comment-15391668 ] ASF GitHub Bot commented on EAGLE-393: -- Github user haoch closed the pull request at:

[jira] [Commented] (EAGLE-394) Fix NPE bug while metadata inconsistent; Fix unit test

[ https://issues.apache.org/jira/browse/EAGLE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391654#comment-15391654 ] ASF GitHub Bot commented on EAGLE-394: -- Github user RalphSu commented on the issue:

[GitHub] incubator-eagle issue #273: EAGLE-394 : fix NPE and broken test

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/273 Quick(might be hurry) JIRA/Open fix to the exception found. --- 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

[jira] [Created] (EAGLE-393) Fix UnitTest Error caused by streamDef.json and TestApplicationImpl

Hao Chen created EAGLE-393: -- Summary: Fix UnitTest Error caused by streamDef.json and TestApplicationImpl Key: EAGLE-393 URL: https://issues.apache.org/jira/browse/EAGLE-393 Project: Eagle Issue

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #94

The Apache Jenkins build system has built incubator-eagle-main (build #94) Status: Failure Check console output at https://builds.apache.org/job/incubator-eagle-main/94/ to view the results. Test Report is at: Test Result

[jira] [Commented] (EAGLE-355) UI advanced policy expression can't parse

[ https://issues.apache.org/jira/browse/EAGLE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391608#comment-15391608 ] ASF GitHub Bot commented on EAGLE-355: -- Github user asfgit closed the pull request at:

[jira] [Commented] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

[ https://issues.apache.org/jira/browse/EAGLE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391550#comment-15391550 ] ASF GitHub Bot commented on EAGLE-392: -- Github user anyway1021 closed the pull request at:

[GitHub] incubator-eagle pull request #274: [EAGLE-392] fix 'relativePath' error of e...

Github user anyway1021 closed the pull request at: https://github.com/apache/incubator-eagle/pull/274 --- 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

Re: Build failure in branch "develop"

This issue has been fixed in develop branch. Michael On Mon, Jul 25, 2016 at 3:07 PM, Zhao, Qingwen wrote: > OK. > > Seems there are some problems in this new branch, which is in the > development and unstable right now. Sorry about that. > > If you are trying Eagle, please

Re: [GitHub] incubator-eagle pull request #274: [EAGLE-392] fix 'relativePath' error of e...

It should be ok to build Eagle/develop branch now. Regards, Qingwen Zhao | Apache Eagle Desk: 20998167 | Cell: +86 18818215025 On 7/25/16, 4:10 PM, "anyway1021" wrote: >GitHub user anyway1021 opened a pull request: > >

[jira] [Commented] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

[ https://issues.apache.org/jira/browse/EAGLE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391530#comment-15391530 ] Michael Wu commented on EAGLE-392: -- modify eagle-core/eagle-common/pom.xml, change artifactId according to

[jira] [Commented] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

[ https://issues.apache.org/jira/browse/EAGLE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391523#comment-15391523 ] ASF GitHub Bot commented on EAGLE-392: -- Github user qingwen220 commented on the issue:

[GitHub] incubator-eagle issue #274: [EAGLE-392] fix 'relativePath' error of eagle-co...

Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/274 LGTM. In Eagle-common pom parent artifactId has been revised --- 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

[GitHub] incubator-eagle pull request #274: [EAGLE-392] fix 'relativePath' error of e...

GitHub user anyway1021 opened a pull request: https://github.com/apache/incubator-eagle/pull/274 [EAGLE-392] fix 'relativePath' error of eagle-common modify eagle-core/eagle-common/pom.xml You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

[ https://issues.apache.org/jira/browse/EAGLE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391513#comment-15391513 ] ASF GitHub Bot commented on EAGLE-392: -- GitHub user anyway1021 opened a pull request:

[GitHub] incubator-eagle pull request #273: develop : fix NPE and broken test

GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/273 develop : fix NPE and broken test 1. avoid mismatch metadata caused serialize/deserialize NPE issue 2. fix broken test in remote branch after merge You can merge this pull request into

Re: Build failure in branch "develop"

OK. Seems there are some problems in this new branch, which is in the development and unstable right now. Sorry about that. If you are trying Eagle, please use the newly released version branch 0.4. If you want to contribute new features, develop branch is ok. For this issue, we are fixing :)

[jira] [Commented] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

[ https://issues.apache.org/jira/browse/EAGLE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391435#comment-15391435 ] Michael Wu commented on EAGLE-392: -- We have to set the tag pointing to the eagle-query-parent/pom.xml

[jira] [Created] (EAGLE-392) "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath"

Michael Wu created EAGLE-392: Summary: "parent" tag in eagle-common/pom.xml is configured incorrectly on "relativePath" Key: EAGLE-392 URL: https://issues.apache.org/jira/browse/EAGLE-392 Project: Eagle

Re: [ANNOUNCE] Apache Eagle 0.4.0-incubating released

Congratulation guys! Great job managing the release. On Wed, Jul 20, 2016 at 8:53 PM, Michael Wu wrote: > Hi, > > The Apache Eagle (incubating) Community is happy to announce the release of > version 0.4.0-incubating from the Apache Incubator. > > Apache Eagle (incubating) is

Re: Build failure in branch "develop"

Yes, I am running mvn from the root folder of the project. Bosco On 7/24/16, 11:29 PM, "Michael Wu" wrote: Just to make sure, are you executing from the project root folder? If you're executing the mvn command from within a sub folder, it may require that