Hi, Christian, No problem. I am glad to help out and as you said, it is a good review of our doc as well.
Regarding to gradlew, I just tried a fresh checkout from http://git-wip-us.apache.org/repos/asf/samza.git and did see the gradlew file there: {noformat} bash-3.2$ pwd /Users/yipan/tmp/tmp-checkout bash-3.2$ ls -l gradlew -rwxr-xr-x 1 yipan LINKEDIN\eng 5080 Jan 15 11:05 *gradlew* {noformat} I even tried to delete the gradlew file and check whether it is tracked by git: {noformat} bash-3.2$ rm gradlew bash-3.2$ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: gradlew no changes added to commit (use "git add" and/or "git commit -a") bash-3.2$ {noformat} The gradlew is clearly tracked and controlled by git repo http://git-wip-us.apache.org/repos/asf/samza.git. I curious why you couldn't find the command. Have you tried a clean git checkout from http://git-wip-us.apache.org/repos/asf/samza.git? On Fri, Jan 15, 2016 at 10:43 AM, Christian Kniep <ckn...@gaikai.com> wrote: > Hey Yi, > > sorry for the confusion, my Java experience is... limit... :) > OK, I have to check out samza first, in hindsight that sounds not too > unreasonable. > But if I read './gradlew' I assume within the samza-checkout there should > be a gradlew file. > ### > root@0437b8c9238a:/opt/apache-samza-0.10.0-src# find . -name gradlew > root@0437b8c9238a:/opt/apache-samza-0.10.0-src# > ### > > Du I have to reference the gradlew file from the hello-samza repository? > > Thanks for walking in my shoes a bit. Let's say afterwards you would have a > howto that serve java-rockies like me as well. :) > > Cheers > Christian > > On Fri, Jan 15, 2016 at 6:45 PM, Yi Pan <nickpa...@gmail.com> wrote: > > > Hi, Christian, > > > > > > The ./gradlew command to publishToMavenLocal should be executed from the > > checkout location of the Samza project, not hello-samza. The tutorial > page > > stated that (from the snippet I copied). Maybe we should make this more > > obvious in the first step: you will need to checkout *both* samza and > > hello-samza repositories if you are working on the latest branch in > > hello-samza. There is a JIRA open that we are trying to combine those two > > together, but for now, those two repositories need to be checked out > > separately and the working combinations are the following: > > - samza latest release branch (e.g. 0.10.0) + hello-samza master. In > this, > > hello-samza master can work out-of-box since all Samza artifacts it needs > > are published and available in the public maven repository > > - samza master branch (e.g. currently 0.10.1) + hello-samza latest. In > > this combination, hello-samza latest do not work out-of-box by itself and > > needs the companion samza master build (i.e. the publishToMavenLocal > build > > command) to make the latest unpublished samza artifacts become available > in > > local box. > > > > Did you try: a) checkout the samza repository in a different directory; > b) > > cd to samza directory and run ./gradlew publishToMavenLocal; c) switch > back > > to hello-samza directory latest branch and run the maven build? If the > > above sequence does not work, please let me know the errors you saw. > > > > Alternatively, you can try to run hello-samza master branch, which will > > automatically pulling in samza artifacts from public maven repo and skip > > the above steps a) and b). > > > > Thanks for making the effort to create an out-of-box docker image for > > hello-samza! > > > > Cheers! > > > > -Yi > > > > On Fri, Jan 15, 2016 at 1:07 AM, Christian Kniep <ckn...@gaikai.com> > > wrote: > > > >> Hey Yi, > >> > >> I checked out the hello-samza project, changed the directory into the > >> project and ran ‘./gradlew’. Since it’s stated ‘./gradlew’ and the file > is > >> present in the project, that’s what I assumed. > >> > >> Cheers > >> Christian > >> -- > >> > >> > >> > >> Christian Kniep | Release Engineer > >> > >> www.gaikai.com > >> > >> On 14 Jan 2016, at 18:58, Yi Pan <nickpa...@gmail.com> wrote: > >> > >> Here is the line from the tutorial: > >> {noformat} > >> > >> NOTE: if you are building from the latest branch of hello-samza project, > >> make sure that you run the following step from your local Samza project > >> first: > >> > >> ./gradlew publishToMavenLocal > >> > >> Then, you can continue w/ the following command in hello-samza project: > >> > >> mvn clean package > >> mkdir -p deploy/samza > >> tar -xvf ./target/hello-samza-0.10.0-dist.tar.gz -C deploy/samza > >> > >> {noformat} > >> > >> On Thu, Jan 14, 2016 at 9:54 AM, Yi Pan <nickpa...@gmail.com> wrote: > >> > >>> Hi, Christian, > >>> > >>> Which local directory are you running ./gradlew publishToMavenLocal > >>> from? The command needs to be executed from the directory under which > the > >>> Samza project is checked out, *not* where the hello-samza project is > >>> checked out. > >>> > >>> -Yi > >>> > >>> On Thu, Jan 14, 2016 at 7:53 AM, Christian Kniep <ckn...@gaikai.com> > >>> wrote: > >>> > >>>> Hey guys, > >>>> > >>>> to rules out that my OS choice had a big effect I followed the steps > on > >>>> the tutorial and created an ubuntu version. > >>>> The README provides my step in detail: > https://github.com/qnib/u-samza > >>>> > >>>> I was not able to execute the gradlew command, maybe that’s my > problem? > >>>> > >>>> Furthermore, when installed via grid - how are the services ZK, kafka > >>>> and yarn are started - the documentation might elaborate a bit on > this to > >>>> help rockies out. > >>>> > >>>> Cheers > >>>> Christian > >>>> > >>>> <Screen Shot 2016-01-14 at 16.48.33.png> > >>>> > >>>> > >>>> -- > >>>> > >>>> > >>>> > >>>> Christian Kniep | Release Engineer > >>>> > >>>> www.gaikai.com > >>>> > >>>> > >>> > >> > >> > > >
