Re: Release?

[Prasad Mujumdar]

   @Julian, strong +1 to making release soon. Thanks for bring that up.
@Ed and @Julien, we did some recent license cleanup (EAGLE-114). Based on
my experience with other incubating project releases (as Julian mentioned,
primarily based on Justin's feedback in past) there some work that still
needed. We EAGLE-115 to tracking that. I will try to prioritize getting a
patch ready for that.

Looks like we don't have a 'how to release' page that outlines the release
steps. Here's a draft that I put together (using some of the existing
incubator project templates).
@Ed and @Arun, if one of you could give me access to the wiki, I can upload
the draft there so that community members can directly edit the page.


*How to Release*

This document describes the release process for Apache Eagle release from
Incubator. This is a working progress document till we have a few releases
and ironed out the process.

*Release manager*

Someone from the community should volunteer to become a release manager(RM)
and coordinate the release process. The release steps listed below will
mostly be carried out by the release manager. Ideally this person should be
a committer or PPMC member, however it should be fine for a contributor to
take that responsibility with one of the committer or PPMC to mentor
him/her to make the release.

The Release Manager (RM) must go through the policy document to understand
all the tasks and responsibilities of running a release.  Frequently asked
questions for making Apache releases are available on Releases FAQ
page. Guide to Release Management
During Incubation

also
has good information on best practices for releasing artifacts from an
incubating Apache project.



*Give a heads up*

The RM should first create an umbrella issue to create the release and then
setup a timeline for release branch point. The community should decide on
the cutoff point for the release branch on the release discussion thread.

To: dev@eagle.incubator.apache.org

Subject: Work on $release release has started


Created a tracking jira (jira#) for the eagle $release and plan to branch
tentatively on $date.



What would you like to see included?

Thanks,

$RM

*Sanitize JIRA*

   1. Before a release is done, make sure that any issues that are *fixed *have
   their fix version setup correctly. Run the following JIRA query to see
   which resolved issues do not have their fix version set up correctly:

   2. project = eagle and resolution = fixed and fixVersion is empty
   3.





   The result of the above query should be empty. If some issues do show up
   in this query that have been fixed since the last release, please bulk-edit
   them to set the fix version to ''.
   4. Move the unresolved jiras to the next release

   5. project = eagle and fixVersion =  and status not in(
   resolved, done, Accepted, Closed)
   6.



   7. You can also run the following query to make sure that the
   issues fixed for the to-be-released version look accurate:

   8. project = eagle and fixVersion = ''
   9.



   10. Finally, check out the output of the *JIRA release note tool*
   

to
   see which JIRAs are included in the release, in order to do a sanity check.

*Creating Release Artifacts*

*Communicate with the community*

   1.  Send an email to dev list to notify that you are about to
   branch. Ask to hold off any commits until this is finished.
   2. Send another email after branching is done.

*Preparing branches*

   1. Create a release branch
  1. Clone fresh repository copy

  2. git clone https://
  git-wip-us.apache.org/repos/asf/incubator-eagle.git
  cd eagle
  3.



  4. Checkout master branch

  5. git checkout master
  6.



  7. Check that current HEAD points to commit on which you want to
  base new  release branch. Checkout particular commit if not.

  8. git log # Check current branch history. HEAD should point to
  commit that you want to be base for your release branch
  git checkout  # Check out particular commit that
  should be base for release branch if -^
  9.



  10. Create new release branch with name "branch-$version"

  11. git checkout -b branch-
  12.



  13. Update CHANGELOG in the trunk to indicate the changes going into
  the new version.
  The change list can be swiped from the *JIRA release note tool*
  

   (use the "text" format for the change log). See JIRA Cleanup above
  to ensure that the release notes generated by this tool are what you are
  expecting.
  14. Remove -SNAPSHOT from the release branch and commit

  15. find . -name pom.xml | xargs sed -i ""
  -e "s/X.Y.0-SNAPSHOT/X.Y.0/"  or  

Re: [Fix Eagle CI Failure] Please help to see if we can fix CI builds

[Prasad Mujumdar]

Hi Michael,

   Thanks for following up on the error. yes, the build does require npm
installed on the machine. You might want to log a INFRA ticket to get that
addressed.
BTW, there's a Jira EAGLE-127 to document npm requirement in the Readme
files.

thanks
Prasad


On Sun, Jan 17, 2016 at 6:47 PM, Michael Wu  wrote:

> Hi guys,
>
> We currently have a failing build #14 at
> https://builds.apache.org/job/incubator-eagle-main/14/console, and from
> the
> console output, I found it failed at step of building eagle-webservice with
> below info:
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2:exec (exec-ui-install) on
> project eagle-webservice: Command execution failed. Process exited
> with an error: 1(Exit value: 1) -> [Help 1][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/MojoExecutionException[ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the command[ERROR]   mvn  -rf :eagle-webservice
>
>
> And, before the error block, there were two rows telling npm not installed:
> ***
>
> Environment Check...
> npm not installed!
>
> ***
>
> Could the lack of npm be the root cause of this failure? If we can confirm
> the need of npm to make our build succeed, I can talk to apache-ci admin
> team and try add it.
>
> Otherwise, if the issue is not caused by npm, please do help to tell me how
> to configure the job to make it pass.
>
> Thanks.
> Michael
>

[jira] [Assigned] (EAGLE-114) Enable RAT check and fix missing license headers

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar reassigned EAGLE-114:
-

Assignee: Prasad Mujumdar

> Enable RAT check and fix missing license headers
> 
>
> Key: EAGLE-114
> URL: https://issues.apache.org/jira/browse/EAGLE-114
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>    Reporter: Prasad Mujumdar
>    Assignee: Prasad Mujumdar
>
> Enable maven rat check plugin to ensue that the source code has Apache 
> license header.



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

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar commented on EAGLE-127:
---

[~yonzhang2012] I can edit the tickets, but still not able to assign myself as 
fixer. I would really appreciate if you could grant me that access in Jira. 
Thanks!

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Priority: Trivial
> Fix For: 0.3.0
>
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar commented on EAGLE-127:
---

Thanks for creating a separate ticket!
We should also mention scala (and for that matter mvn). It would be good to 
list all the dev tools required for the build. I can update the README.

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Priority: Trivial
> Fix For: 0.3.0
>
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

[jira] [Commented] (EAGLE-127) add NPM as pre-requisite for mvn eagle build

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar commented on EAGLE-127:
---

Thanks!
Normally adding a contributor roles in Jira is sufficient for that. If that's 
not working, then I can log a infra ticket. Again, thanks for all the help!

> add NPM as pre-requisite for mvn eagle build
> 
>
> Key: EAGLE-127
> URL: https://issues.apache.org/jira/browse/EAGLE-127
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>    Assignee: Prasad Mujumdar
>Priority: Trivial
> Fix For: 0.3.0
>
>
> NPM should be installed before mvn build. Normally people don't realize it is 
> because of NPM if the build fails. I think we should explicitly say we need 
> install NPM before mvn build.



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

[jira] [Resolved] (EAGLE-114) Enable RAT check and fix missing license headers

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar resolved EAGLE-114.
---
Resolution: Fixed

Patch pulled in master.
Thanks [~haoch] for the review and merge!

> Enable RAT check and fix missing license headers
> 
>
> Key: EAGLE-114
> URL: https://issues.apache.org/jira/browse/EAGLE-114
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>    Reporter: Prasad Mujumdar
>
> Enable maven rat check plugin to ensue that the source code has Apache 
> license header.



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

Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check

[Prasad Mujumdar]

   Thanks!
I guess we have enough consensus  to add rat check by default. I will keep
the current PR as is. We can discuss the details of the followup issue of
 about webapp files on the Jira ticket. We can close this thread.

I would appreciate if somebody can take a look at PR #51 [3]

thanks
Prasad

[3] - https://github.com/apache/incubator-eagle/pull/51

On Mon, Jan 4, 2016 at 6:41 PM, Chen, Hao <hao.ch...@ebay.com> wrote:

> I think it’s a good suggestion, please move ahead to enable it by default
> and fix the missing license headers.
>
> Thanks,
> Hao
>
>
>
> On 1/5/16, 5:58 AM, "Don Bosco Durai" <bo...@apache.org> wrote:
>
> >I agree, it is better if it is enabled by default. At least in Ranger we
> have seen builds failing and we scrambling to fix the build.
> >
> >Bosco
> >
> >
> >
> >
> >On 1/2/16, 11:51 PM, "Prasad Mujumdar" <p3mujum...@gmail.com> wrote:
> >
> >>Hey Hao,
> >>
> >> Thanks for clarifying that.
> >>
> >>When it's forced in the build, the owners is on every developer to ensure
> >>that the new files have the correct license header. They can fix any
> >>missing files locally (or add an exception when applicable). Keeping this
> >>in CI or release build makes the process longer and requires more
> iteration
> >>for each patch/release.
> >>Let me know if it's still preferred in CI. The header updates in the PR
> are
> >>still needed.
> >>
> >>thanks
> >>Prasad
> >>
> >>
> >>On Sat, Jan 2, 2016 at 10:36 PM, Hao Chen <cn.haoc...@gmail.com> wrote:
> >>
> >>> Hi Prasad,
> >>>
> >>> Thanks for it. We declared RAT in pom plugin management and enable by
> >>> command arguments when necessary but not forcefully, which would be
> added
> >>> in CI.
> >>>
> >>> Thanks,
> >>> Hao
> >>>
> >>> > On Jan 3, 2016, at 12:01 PM, Prasad Mujumdar <p3mujum...@gmail.com>
> >>> wrote:
> >>> >
> >>> > Hello Hao,
> >>> >
> >>> >   There's RAT plugin defined under plugin management, however it's
> not
> >>> > enabled. Also there are a number of files that are missing the
> license
> >>> > header. I just submitted the PR #51 [2] that adds license header to
> 26
> >>> > files, plus the ones under webapp still needs to be handled.
> >>> >
> >>> > thanks
> >>> > Prasad
> >>> >
> >>> > [2] - https://github.com/apache/incubator-eagle/pull/51
> >>> >
> >>> >> On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen <cn.haoc...@gmail.com>
> wrote:
> >>> >>
> >>> >> RAT has already been enabled in the pom when open source.
> >>> >>
> >>> >>>> On Jan 3, 2016, at 6:30 AM, Edward Zhang <yonzhang2...@apache.org
> >
> >>> >>> wrote:
> >>> >>>
> >>> >>> Good point to have tools to identify missing license header, we
> should
> >>> >> have
> >>> >>> that.
> >>> >>>
> >>> >>> In terms of license headers under eagle-webservice, I remembered
> there
> >>> >> was
> >>> >>> some discussion on the license of those files, probably Jilin can
> >>> provide
> >>> >>> more details.
> >>> >>>
> >>> >>> Thanks
> >>> >>>
> >>> >>> Edward
> >>> >>>
> >>> >>>> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar <
> pras...@apache.org>
> >>> >> wrote:
> >>> >>>>
> >>> >>>> Hi,
> >>> >>>>
> >>> >>>>  Looks like we have a bunch of files that are missing the Apache
> >>> >> license
> >>> >>>> headers. IMO it's a good idea to add the Maven RAT plugin to
> ensure
> >>> that
> >>> >>>> every new file has license header. Otherwise the responsibility
> falls
> >>> on
> >>> >>>> the release manager's head to correct it and makes the release
> process
> >>> >>>> longer and tedious.
> >>> >>>> I have logged a ticket EAGLE-114 [1] to track it and got a working
> >>> patch
> >>> >>>> that I can submit a PR. One of the problem fileset is the webapp
> under
> >>> >>>> eagle-webservice. There are a large number of files which don't
> have
> >>> >>>> license header. I would like to create a separate ticket to track
> >>> which
> >>> >>>> files should have the header and which should be excluded.
> >>> >>>>
> >>> >>>> Let me know if that sounds reasonable.
> >>> >>>>
> >>> >>>> thanks
> >>> >>>> Prasad
> >>> >>>>
> >>> >>>> [1] - https://issues.apache.org/jira/browse/EAGLE-114
> >>> >>
> >>>
> >
>

Re: January 2016 Report

[Prasad Mujumdar]

   +1 to the nice summary!

Perhaps the details under those sections, like new contributors and release
plan etc can be moved under "How has the community developed" section ?

thanks
Prasad


On Mon, Jan 4, 2016 at 12:49 AM, amareshwarisr . 
wrote:

> Hi,
>
> I see the report for Eagle has been updated on wiki -
> http://wiki.apache.org/incubator/January2016.
>
> Nicely summarised report!
>
> Have a couple of comments :
>
>- Following sentence is incomplete :
>
>   1. We have submitted papers and applied to conferences. We worked
> with other open source projects like
>
>
>- For Date of last release and When were last committers added - you can
>put it as NONE.
>
> Thanks
> Amareshwari
>
> On Thu, Dec 31, 2015 at 3:30 AM, Marvin Humphrey 
> wrote:
>
> > Greetings, {podling} developers!
> >
> > This is a reminder that your report is due next Wednesday, January
> > 6th.  Details below.
> >
> > Best,
> >
> > Marvin Humphrey, Report Manager for January, on behalf of the
> > Incubator PMC
> >
> > ---
> >
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 20 January 2016, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, January 6th).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > http://wiki.apache.org/incubator/January2016
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> >
>

[jira] [Created] (EAGLE-114) Enable RAT check and fix missing license headers

[Prasad Mujumdar (JIRA)]

Prasad Mujumdar created EAGLE-114:
-

 Summary: Enable RAT check and fix missing license headers
 Key: EAGLE-114
 URL: https://issues.apache.org/jira/browse/EAGLE-114
 Project: Eagle
  Issue Type: Improvement
Affects Versions: 0.3.0
Reporter: Prasad Mujumdar


Enable maven rat check plugin to ensue that the source code has Apache license 
header.



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

Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check

[Prasad Mujumdar]

Hello Hao,

   There's RAT plugin defined under plugin management, however it's not
enabled. Also there are a number of files that are missing the license
header. I just submitted the PR #51 [2] that adds license header to 26
files, plus the ones under webapp still needs to be handled.

thanks
Prasad

[2] - https://github.com/apache/incubator-eagle/pull/51

On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen <cn.haoc...@gmail.com> wrote:

> RAT has already been enabled in the pom when open source.
>
> > On Jan 3, 2016, at 6:30 AM, Edward Zhang <yonzhang2...@apache.org>
> wrote:
> >
> > Good point to have tools to identify missing license header, we should
> have
> > that.
> >
> > In terms of license headers under eagle-webservice, I remembered there
> was
> > some discussion on the license of those files, probably Jilin can provide
> > more details.
> >
> > Thanks
> >
> > Edward
> >
> >> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar <pras...@apache.org>
> wrote:
> >>
> >> Hi,
> >>
> >>   Looks like we have a bunch of files that are missing the Apache
> license
> >> headers. IMO it's a good idea to add the Maven RAT plugin to ensure that
> >> every new file has license header. Otherwise the responsibility falls on
> >> the release manager's head to correct it and makes the release process
> >> longer and tedious.
> >> I have logged a ticket EAGLE-114 [1] to track it and got a working patch
> >> that I can submit a PR. One of the problem fileset is the webapp under
> >> eagle-webservice. There are a large number of files which don't have
> >> license header. I would like to create a separate ticket to track which
> >> files should have the header and which should be excluded.
> >>
> >> Let me know if that sounds reasonable.
> >>
> >> thanks
> >> Prasad
> >>
> >> [1] - https://issues.apache.org/jira/browse/EAGLE-114
> >>
>

Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check

[Prasad Mujumdar]

Hey Hao,

 Thanks for clarifying that.

When it's forced in the build, the owners is on every developer to ensure
that the new files have the correct license header. They can fix any
missing files locally (or add an exception when applicable). Keeping this
in CI or release build makes the process longer and requires more iteration
for each patch/release.
Let me know if it's still preferred in CI. The header updates in the PR are
still needed.

thanks
Prasad


On Sat, Jan 2, 2016 at 10:36 PM, Hao Chen <cn.haoc...@gmail.com> wrote:

> Hi Prasad,
>
> Thanks for it. We declared RAT in pom plugin management and enable by
> command arguments when necessary but not forcefully, which would be added
> in CI.
>
> Thanks,
> Hao
>
> > On Jan 3, 2016, at 12:01 PM, Prasad Mujumdar <p3mujum...@gmail.com>
> wrote:
> >
> > Hello Hao,
> >
> >   There's RAT plugin defined under plugin management, however it's not
> > enabled. Also there are a number of files that are missing the license
> > header. I just submitted the PR #51 [2] that adds license header to 26
> > files, plus the ones under webapp still needs to be handled.
> >
> > thanks
> > Prasad
> >
> > [2] - https://github.com/apache/incubator-eagle/pull/51
> >
> >> On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen <cn.haoc...@gmail.com> wrote:
> >>
> >> RAT has already been enabled in the pom when open source.
> >>
> >>>> On Jan 3, 2016, at 6:30 AM, Edward Zhang <yonzhang2...@apache.org>
> >>> wrote:
> >>>
> >>> Good point to have tools to identify missing license header, we should
> >> have
> >>> that.
> >>>
> >>> In terms of license headers under eagle-webservice, I remembered there
> >> was
> >>> some discussion on the license of those files, probably Jilin can
> provide
> >>> more details.
> >>>
> >>> Thanks
> >>>
> >>> Edward
> >>>
> >>>> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar <pras...@apache.org>
> >> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>>  Looks like we have a bunch of files that are missing the Apache
> >> license
> >>>> headers. IMO it's a good idea to add the Maven RAT plugin to ensure
> that
> >>>> every new file has license header. Otherwise the responsibility falls
> on
> >>>> the release manager's head to correct it and makes the release process
> >>>> longer and tedious.
> >>>> I have logged a ticket EAGLE-114 [1] to track it and got a working
> patch
> >>>> that I can submit a PR. One of the problem fileset is the webapp under
> >>>> eagle-webservice. There are a large number of files which don't have
> >>>> license header. I would like to create a separate ticket to track
> which
> >>>> files should have the header and which should be excluded.
> >>>>
> >>>> Let me know if that sounds reasonable.
> >>>>
> >>>> thanks
> >>>> Prasad
> >>>>
> >>>> [1] - https://issues.apache.org/jira/browse/EAGLE-114
> >>
>

[jira] [Commented] (EAGLE-103) add comments to readme to tell users: currently, eagle is tested under jdk1.7.x, may have compile error with jdk1.8.x

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar commented on EAGLE-103:
---

  It would be nice to add other requirements like scala,  npm and maven in the 
REAME. Typically ASF project readme would list all the required tools for 
building the project.

> add comments to readme to tell users: currently, eagle is tested under 
> jdk1.7.x, may have compile error with jdk1.8.x
> -
>
> Key: EAGLE-103
> URL: https://issues.apache.org/jira/browse/EAGLE-103
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Hao Chen
>Priority: Minor
>
> Compilation error found while building with JDK1.8.x (refer to 
> https://issues.apache.org/jira/browse/EAGLE-101).
> I think we should update the required version of jdk in readme file of the 
> project.



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

Re: unit test fails while build incubator-eagle

[Prasad Mujumdar]

   Created EAGLE-104 <https://issues.apache.org/jira/browse/EAGLE-104> to
track the issue and attached the patch. will run the tests and submit pull
request.
Are we suppose to use ReviewBoard or some other tool for code reviews ?

thanks
Prasad


On Mon, Dec 28, 2015 at 1:37 AM, Prasad Mujumdar <pras...@apache.org> wrote:

>
>   Looks like the problem is that the UGI parsing method is not handling
> the simple authentication scenario where user name is not a kerberos
> principal. I can log a ticket and submit a patch if nobody else is looking
> into this.
>
> thanks
> Prasad
>
>
> On Sun, Dec 27, 2015 at 9:27 PM, Michael Wu <mchl@gmail.com> wrote:
>
>> Hi guys,
>>
>> While I was trying to kick off a build at
>> https://builds.apache.org/job/incubator-eagle-pr-reviewer, an exception
>> was
>> thrown out from a unit test method with the message pasted at the bottom.
>> Could anyone who is responsible for this unit test to take a look and fix
>> it, please? Otherwise it may block pull requests from getting passed for
>> CI
>> verification.
>> Error message from Unit test:
>> **
>> 
>> 
>> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>> at
>> java.lang.String.substring(String.java:1911) at
>>
>> org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
>> at
>>
>> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
>> at
>>
>> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
>> at
>>
>> org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606) at
>>
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>> at
>>
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>> at
>>
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>> at
>>
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at
>>
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>> at
>>
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at
>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at
>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at
>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at
>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at
>> org.junit.runners.ParentRunner.run(ParentRunner.java:300) at
>>
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
>> at org.apache.maven.surefire.Surefire.run(Surefire.java:169) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606) at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
>> at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
>> 
>> 
>> log4j:WARN No appenders could be found for logger
>> (org.apache.eagle.common.config.EagleConfigFactory). log4j:WARN Please
>> initialize the log4j system properly. log4j:WARN See
>> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>> 
>> 
>> **
>>
>> To get more detailed info about the error, please refer to
>>
>> https://builds.apache.org/job/incubator-eagle-pr-reviewer/ws/eagle-security/eagle-security-hdfs-securitylog/target/surefire-reports/
>>
>> Thanks.
>> Michael
>>
>
>

[jira] [Created] (EAGLE-104) Fix the unit test TestHDFSSecuritylogParser

[Prasad Mujumdar (JIRA)]

Prasad Mujumdar created EAGLE-104:
-

 Summary: Fix the unit test TestHDFSSecuritylogParser  
 Key: EAGLE-104
 URL: https://issues.apache.org/jira/browse/EAGLE-104
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Prasad Mujumdar


The test fails with following error
{noformat}
java.lang.StringIndexOutOfBoundsException">
java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
java.lang.String.substring(String.java:1911) at
org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
at
org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
at
org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
at
org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
{noformat}

Looks like the problem is that the UGI parsing method is not handling the 
simple authentication scenario where user name is not a kerberos principal. 



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

Requesting contributor access to Jira

[Prasad Mujumdar]

Hello,

  I would be interested in contributing to the project. Requesting
contributor access to the Jira so that I can assign tickets to myself.

thanks
Prasad

[jira] [Updated] (EAGLE-104) Fix the unit test TestHDFSSecuritylogParser

[Prasad Mujumdar (JIRA)]

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

Prasad Mujumdar updated EAGLE-104:
--
Attachment: EAGLE-104.1.patch

> Fix the unit test TestHDFSSecuritylogParser  
> -
>
> Key: EAGLE-104
> URL: https://issues.apache.org/jira/browse/EAGLE-104
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>    Reporter: Prasad Mujumdar
> Attachments: EAGLE-104.1.patch
>
>
> The test fails with following error
> {noformat}
> java.lang.StringIndexOutOfBoundsException">
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
> java.lang.String.substring(String.java:1911) at
> org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
> at
> org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
> {noformat}
> Looks like the problem is that the UGI parsing method is not handling the 
> simple authentication scenario where user name is not a kerberos principal. 



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