Hello Vikram, Thanks for your help and contribution.
The normal flow is that you create an Issue (what you have done with Olingo-355) and then attach the contribution (e.g. a bugfix) as "diff" file (e.g. created via "git diff > patch.diff" [http://git-scm.com/docs/git-diff]) to the issue. Afterwards a project member with commit rights have to check the contribution and commit it into the git repository. Your mentioned error "Rat check" is caused by files within your project structure which do not have a correct license header. Can you please check the rat report file (the path of it is shown beside the error/summary line). If you have more questions, do not hesitate to ask ;o) Kind regards, Michael On 10.07.14 12:50, "Vikram Pancholi" <[email protected]> wrote: >Hi, > I am new committer to ASF/Olingo here. I ahev logged a minor issue >regarding antlr and eclipse import Olingo 355. Can you please point me to >a >process flow document on how to commit the modification. > >Till now I have created a branch on my local machine. >When I do a mvn clean install I am getting an error >"Rat check : Summary of files. Unapproved : 1 unknown generated : 0 >approved : 5 license". >Also correct if i am wrong , I am creating a branch with issue name olingo >355 in my case. I should be pushing the same to git and one of the >moderator would merge this change into master ? > >Regards, >Vikram Pancholi
smime.p7s
Description: S/MIME cryptographic signature
