[jira] [Commented] (EAGLE-500) inaccurate IllegalStateException not caught within unit-test-cases when MongoDB normal stop() fails

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

Re: Branch "develop" is failing due to org.apache.eagle.service.alert.resource.impl.MongoImplTest

https://github.com/apache/incubator-eagle/pull/387 opened, please review if the solution makes sense. On Thu, Aug 25, 2016 at 11:58 AM, Michael Wu wrote: > https://issues.apache.org/jira/browse/EAGLE-500 created. > > On Thu, Aug 25, 2016 at 10:24 AM, Hao Chen

[GitHub] incubator-eagle pull request #387: [EAGLE-500] fix process-stopping issue of...

GitHub user anyway1021 opened a pull request: https://github.com/apache/incubator-eagle/pull/387 [EAGLE-500] fix process-stopping issue of mongodb unit test case https://issues.apache.org/jira/browse/EAGLE-500 You can merge this pull request into a Git repository by running: $

RE: Please take notice to check-in only meaningful javadoc.

Currently I ignored java doc check in checkstyle configuration: https://github.com/apache/incubator-eagle/blob/develop/eagle-dev/checkstyle.xml#L236 -Original Message- From: Michael Wu [mailto:mchl@gmail.com] Sent: 2016年8月25日 13:09 To: dev@eagle.incubator.apache.org Subject: Re:

[jira] [Created] (EAGLE-501) add attempt fields to mr history job entity

wujinhu created EAGLE-501: - Summary: add attempt fields to mr history job entity Key: EAGLE-501 URL: https://issues.apache.org/jira/browse/EAGLE-501 Project: Eagle Issue Type: New Feature

[GitHub] incubator-eagle pull request #386: Change resourceFetch to resourcefetch

Github user qingwen220 closed the pull request at: https://github.com/apache/incubator-eagle/pull/386 --- 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: Please take notice to check-in only meaningful javadoc.

No, for most buildings including PR verification, develop check-in, we don't have to run javadoc phase. The issue was exposed when I tried to deploy snapshot artifacts, using jdk1.8.x to compile and execute deploying commands which include the javadoc phase by default. On Thu, Aug 25, 2016 at

Re: Please take notice to check-in only meaningful javadoc.

Run 'mvn javadoc:javadoc javadoc:test-javadoc', it now immediately failed :-( So looks like mvn javadoc can find out useless param. Do we need do both checkstyle and javadoc while in building? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc

[jira] [Commented] (EAGLE-407) storm bolt error:java.lang.RuntimeException: java.util.regex.PatternSyntaxException: Illegal repetition near index 1 ./{} ^

[ https://issues.apache.org/jira/browse/EAGLE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436256#comment-15436256 ] rube.q commented on EAGLE-407: -- have you fixed it ? > storm bolt error:java.lang.RuntimeException: >

[GitHub] incubator-eagle pull request #386: Change resourceFetch to resourcefetch

GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/386 Change resourceFetch to resourcefetch Fix compilation error：” import org.apache.eagle.jpm.util.resourcefetch.model.AppInfo ” not found You can merge this pull request into a Git

[jira] [Created] (EAGLE-500) inaccurate IllegalStateException not caught within unit-test-cases when MongoDB normal stop() fails

Michael Wu created EAGLE-500: Summary: inaccurate IllegalStateException not caught within unit-test-cases when MongoDB normal stop() fails Key: EAGLE-500 URL: https://issues.apache.org/jira/browse/EAGLE-500

Re: Branch "develop" is failing due to org.apache.eagle.service.alert.resource.impl.MongoImplTest

https://issues.apache.org/jira/browse/EAGLE-500 created. On Thu, Aug 25, 2016 at 10:24 AM, Hao Chen wrote: > Branch "develop" is failing due to > "org.apache.eagle.service.alert.resource.impl.MongoImplTest" which is > really unstable, could anybody help fix it? >

[GitHub] incubator-eagle pull request #385: [Eagle-499] Fix flushing entities for spa...

GitHub user pkuwm opened a pull request: https://github.com/apache/incubator-eagle/pull/385 [Eagle-499] Fix flushing entities for spark history job You can merge this pull request into a Git repository by running: $ git pull https://github.com/pkuwm/incubator-eagle EAGLE-499

[jira] [Created] (EAGLE-499) Fix flushing entities for spark history job.

Huizhi Lu created EAGLE-499: --- Summary: Fix flushing entities for spark history job. Key: EAGLE-499 URL: https://issues.apache.org/jira/browse/EAGLE-499 Project: Eagle Issue Type: Bug Affects

Re: [Question] Is SiteResource Thread Safe?

Basically for any metadata persistence function, 1) you should firstly define a interface say SomeService interface SomeService { void doSomeThing(); } 2) Then you need to implement the interface for different kind of storeage type say memory (test purpose only), jdbc and mongodb, and bind

[jira] [Resolved] (EAGLE-496) Fix code style of JPM

[ https://issues.apache.org/jira/browse/EAGLE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu resolved EAGLE-496. --- Resolution: Resolved > Fix code style of JPM > - > > Key: EAGLE-496 >

[jira] [Closed] (EAGLE-496) Fix code style of JPM

[ https://issues.apache.org/jira/browse/EAGLE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-496. - > Fix code style of JPM > - > > Key: EAGLE-496 > URL:

[jira] [Commented] (EAGLE-496) Fix code style of JPM

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

[GitHub] incubator-eagle pull request #383: [EAGLE-496] fix code style of jpm

Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/383 --- 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-472) Fix HBase unit test

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

Re: [DISCUSS] Is Eagle ready to graduate?

Hi mentors, I will update security page content taking the mentioned aspects. Except for the security part, is there any other gaps that you feel eagle has to fill before graduation? Please feel free to point issues out and we will do our best to get aligned to what graduation requires. Thanks.

[GitHub] incubator-eagle pull request #357: [EAGLE-472] Fix HBase unit test

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

[GitHub] incubator-eagle issue #357: [EAGLE-472] Fix HBase unit test

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/357 @baibaichen pls. close 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

[jira] [Commented] (EAGLE-472) Fix HBase unit test

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

[jira] [Assigned] (EAGLE-498) overwrite equals method for PolicyDefinition should not contain field description

[ https://issues.apache.org/jira/browse/EAGLE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lingang Deng reassigned EAGLE-498: -- Assignee: Lingang Deng (was: JiJun Tang) > overwrite equals method for PolicyDefinition should

[GitHub] incubator-eagle pull request #384: EAGLE-498 overwrite equals method for Pol...

GitHub user chitin opened a pull request: https://github.com/apache/incubator-eagle/pull/384 EAGLE-498 overwrite equals method for PolicyDefinition should not con… EAGLE-498 overwrite equals method for PolicyDefinition should not contain field description - Delete the

[jira] [Updated] (EAGLE-498) overwrite equals method for PolicyDefinition should not contain field description

[ https://issues.apache.org/jira/browse/EAGLE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lingang Deng updated EAGLE-498: --- Description: Overwrite equals method for PolicyDefinition should not contain field "description", it

[jira] [Created] (EAGLE-498) overwrite equals method for PolicyDefinition should not contain field description

Lingang Deng created EAGLE-498: -- Summary: overwrite equals method for PolicyDefinition should not contain field description Key: EAGLE-498 URL: https://issues.apache.org/jira/browse/EAGLE-498 Project:

[jira] [Commented] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

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

[GitHub] incubator-eagle pull request #375: [EAGLE-492] Fix negative total execution ...

Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/375 --- 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 FAILED] incubator-eagle-develop failed on build #61

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

[GitHub] incubator-eagle issue #375: [EAGLE-492] Fix negative total execution time an...

Github user DadanielZ commented on the issue: https://github.com/apache/incubator-eagle/pull/375 merged, plz close 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

[GitHub] incubator-eagle pull request #382: [EAGLE-484][EAGLE-497] Add override equal...

Github user r7raul1984 closed the pull request at: https://github.com/apache/incubator-eagle/pull/382 --- 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] [Closed] (EAGLE-497) Fix code style of Oozie

[ https://issues.apache.org/jira/browse/EAGLE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang closed EAGLE-497. > Fix code style of Oozie > --- > > Key: EAGLE-497 > URL:

[jira] [Resolved] (EAGLE-497) Fix code style of Oozie

[ https://issues.apache.org/jira/browse/EAGLE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang resolved EAGLE-497. -- Resolution: Fixed > Fix code style of Oozie > --- > > Key: EAGLE-497

[jira] [Commented] (EAGLE-492) Fix negative total execution time and make some code optimization for spark history job.

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

[GitHub] incubator-eagle issue #375: [EAGLE-492] Fix negative total execution time an...

Github user pkuwm commented on the issue: https://github.com/apache/incubator-eagle/pull/375 It was because of the conflicts with the previous check style commit. I have fixed it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[jira] [Closed] (EAGLE-483) Test email alert publisher

[ https://issues.apache.org/jira/browse/EAGLE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-483. --- > Test email alert publisher > -- > > Key: EAGLE-483 >

[jira] [Resolved] (EAGLE-483) Test email alert publisher

[ https://issues.apache.org/jira/browse/EAGLE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu resolved EAGLE-483. - Resolution: Fixed > Test email alert publisher > -- > > Key:

[GitHub] incubator-eagle pull request #365: Test email alert publisher: configuration...

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

[GitHub] incubator-eagle issue #375: [EAGLE-492] Fix negative total execution time an...

Github user DadanielZ commented on the issue: https://github.com/apache/incubator-eagle/pull/375 Patch apply failed, please fix it first. error: patch failed: eagle-jpm/eagle-jpm-entity/src/main/java/org/apache/eagle/jpm/spark/crawl/JHFSparkEventReader.java:21 error:

[GitHub] incubator-eagle issue #365: Test email alert publisher: configuration and co...

Github user DadanielZ commented on the issue: https://github.com/apache/incubator-eagle/pull/365 merged, please close it. --- 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

[jira] [Updated] (EAGLE-495) Convert spark history job using application framework

[ https://issues.apache.org/jira/browse/EAGLE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu updated EAGLE-495: Remaining Estimate: 60h Original Estimate: 60h > Convert spark history job using application framework

Re: Please take notice to check-in only meaningful javadoc.

This bugs me too. FWIW, in Calcite we run ‘mvn javadoc:javadoc javadoc:test-javadoc’ as part of the automated build (as of JDK 1.8, javadoc is quite strict). Neither javadoc nor checkstyle will flag useless javadoc like ‘@param x’, so I wrote a checkstyle module[1] and call it from Calcite’s

Re: [Question] Is SiteResource Thread Safe?

Hi Edward Do you mean implement SiteEntityEntityServiceJDBCImpl and ApplicationEntityJDBCImpl, so that we can bind them in JDBCMetadataStore? i.e. bind(SiteEntityService.class).to(SiteEntityEntityServiceJDBCI mpl .class).in(Singleton.class);

[jira] [Commented] (EAGLE-496) Fix code style of JPM

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

[jira] [Commented] (EAGLE-460) Convert MR running app with new app framework

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

[GitHub] incubator-eagle issue #383: [EAGLE-496] fix code style of jpm

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/383 Pls. close 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

[EAGLE BUILD FAILED] incubator-eagle-develop failed on build #58

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

[GitHub] incubator-eagle issue #383: [EAGLE-496] fix code style of jpm

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/383 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

[jira] [Commented] (EAGLE-496) Fix code style of JPM

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

[jira] [Commented] (EAGLE-484) StreamRouterSpec class should override equals method

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

[GitHub] incubator-eagle issue #382: [EAGLE-484][EAGLE-497] Add override equals metho...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/382 @r7raul1984 Merged, pls. close 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

[jira] [Commented] (EAGLE-321) java.lang.NoSuchMethodError: com.google.protobuf.LazyStringList.getUnmodifiableView

[ https://issues.apache.org/jira/browse/EAGLE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434725#comment-15434725 ] rube.q commented on EAGLE-321: -- I use 0.4.0,how to fix it by myself? > java.lang.NoSuchMethodError: >

[jira] [Commented] (EAGLE-496) Fix code style of JPM

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

[GitHub] incubator-eagle pull request #383: [EAGLE-496] fix code style of jpm

GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/383 [EAGLE-496] fix code style of jpm You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-496 Alternatively you

[jira] [Commented] (EAGLE-497) Fix code style of Oozie

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

[jira] [Commented] (EAGLE-484) StreamRouterSpec class should override equals method

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

[GitHub] incubator-eagle pull request #369: [EAGLE-484] StreamRouterSpec class should...

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

[GitHub] incubator-eagle issue #382: EAGLE-497 Fix code style of Oozie

Github user r7raul1984 commented on the issue: https://github.com/apache/incubator-eagle/pull/382 I will close #369 --- 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

[jira] [Commented] (EAGLE-348) Alert engine base on spark streaming

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

[GitHub] incubator-eagle issue #379: EAGLE-348 Alert engine base on spark streaming

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/379 One of the target is to make sure alert engine could be decoupled to run on both Storm and Spark, while they should share the same metadata, I don't understand why do we need spark specific

[GitHub] incubator-eagle issue #382: EAGLE-497 Fix code style of Oozie

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/382 Seems to have duplicated commits with #369 ? --- 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

[jira] [Commented] (EAGLE-497) Fix code style of Oozie

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

[jira] [Commented] (EAGLE-497) Fix code style of Oozie

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

[GitHub] incubator-eagle pull request #382: EAGLE-497 Fix code style of Oozie

GitHub user r7raul1984 opened a pull request: https://github.com/apache/incubator-eagle/pull/382 EAGLE-497 Fix code style of Oozie EAGLE-497 Fix code style of Oozie - Fix code style of Oozie https://issues.apache.org/jira/browse/EAGLE-497 You can merge this pull

[jira] [Commented] (EAGLE-495) Convert spark history job using application framework

[ https://issues.apache.org/jira/browse/EAGLE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434540#comment-15434540 ] Hao Chen commented on EAGLE-495: [~hzlu] Pls. go ahead if you would like to take this ticket, but could you

[GitHub] incubator-eagle pull request #381: EAGLE-460 Convert MR running app with new...

GitHub user haoch opened a pull request: https://github.com/apache/incubator-eagle/pull/381 EAGLE-460 Convert MR running app with new app framework https://issues.apache.org/jira/browse/EAGLE-460 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (EAGLE-460) Convert MR running app with new app framework

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

[jira] [Created] (EAGLE-497) Fix code style of Oozie

JiJun Tang created EAGLE-497: Summary: Fix code style of Oozie Key: EAGLE-497 URL: https://issues.apache.org/jira/browse/EAGLE-497 Project: Eagle Issue Type: Improvement Reporter:

[jira] [Commented] (EAGLE-461) Convert MR history app with new app framework

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

[GitHub] incubator-eagle issue #380: EAGLE-461 Convert MR history app with new app fr...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/380 Merged and closed. --- 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

[jira] [Commented] (EAGLE-461) Convert MR history app with new app framework

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

[GitHub] incubator-eagle pull request #380: EAGLE-461 Convert MR history app with new...

Github user haoch closed the pull request at: https://github.com/apache/incubator-eagle/pull/380 --- 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] [Created] (EAGLE-496) Fix code style of JPM

wujinhu created EAGLE-496: - Summary: Fix code style of JPM Key: EAGLE-496 URL: https://issues.apache.org/jira/browse/EAGLE-496 Project: Eagle Issue Type: Improvement Reporter: wujinhu

[jira] [Closed] (EAGLE-488) fix not delete finished application path in zk and jobDefId issues

[ https://issues.apache.org/jira/browse/EAGLE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-488. - > fix not delete finished application path in zk and jobDefId issues >

[jira] [Closed] (EAGLE-494) add fields to mr history job entity

[ https://issues.apache.org/jira/browse/EAGLE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-494. - > add fields to mr history job entity > --- > > Key: EAGLE-494 >

[jira] [Commented] (EAGLE-494) add fields to mr history job entity

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

[GitHub] incubator-eagle pull request #377: [EAGLE-494] add fields to mr history job ...

Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/377 --- 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-494) add fields to mr history job entity

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

[GitHub] incubator-eagle issue #377: [EAGLE-494] add fields to mr history job entity

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/377 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

Re: Please take notice to check-in only meaningful javadoc.

Good reminding. @Contributors, not only about java docs, pls. make sure all the code style matches the checkstyle, currently I just keep the checkstyle as WARNING as we still have lots of style warning to clean, in future we should throw ERROR if any check-style doesn't match. Pls. start to spend

Please take notice to check-in only meaningful javadoc.

Hi guys, Recently, when I tried to deploy eagle 0.5.0-incubating-snapshot artifacts based on develop branch, the entire build flow was broken by lots of faulty javadoc, which are classified in following aspects. I'll try to erase illegal/meaningless javadoc, and please PAY ATTENTION to your