Actually, it looks like I was using an older version of the tutorial instead of the latest.
http://samza.apache.org/startup/hello-samza/latest/ With the latest version, I see the same issue you reported: > Access denied to: > https://oss.sonatype.org/content/groups/scala-tools/org/apache/samza/samza-api/0.11.0-SNAPSHOT/samza-api-0.11.0-SNAPSHOT.pom Still, I will file a ticket. Thanks for reporting the issue! On Fri, Aug 12, 2016 at 11:12 AM, Jacob Maes <jacob.m...@gmail.com> wrote: > It does seem that the instructions need some clarification. > > They certainly need updating. For example I noticed they still reference > the old 10.0 version in the tgz file. > > I'll create a ticket to fix the discrepancies. > > Thanks! > > On Fri, Aug 12, 2016 at 10:30 AM, Ryan Brown <ryankbr...@gmail.com> wrote: > >> Jacob, >> >> Thanks for the quick reply. I decided to skip step one and I looked at my >> pom. IT matches the one in the latest which they tell you to checkout in >> the instructions. If I stay on master it compiles fine. Thanks for >> pointing >> that out! It does seem that the instructions need some clarification. Or >> maybe just my brain? >> >> -rb >> >> On Fri, Aug 12, 2016 at 11:01 AM, Jacob Maes <jacob.m...@gmail.com> >> wrote: >> >> > Hey Ryan, >> > >> > There are a couple things I noticed at first glance: >> > 1. According to the hello-samza tutorial instructions, >> > "publishToMavenLocal" should be run from a local copy of samza if you >> have >> > one. It should not be run from hello-samza >> > 2. Possibly related to #1. It seems that your mvn package is pulling >> samza >> > 11.0 SNAPSHOT. I just ran through the tutorial and mine was pulling >> 10.1. >> > Did you modify the pom.xml by chance?' >> > >> > -Jake >> > >> > On Fri, Aug 12, 2016 at 9:28 AM, Ryan Brown <ryankbr...@gmail.com> >> wrote: >> > >> > > I am trying to follow the hello-samza >> > > <https://samza.apache.org/startup/hello-samza/latest/> basic setup >> and >> > > cannot get past "Build a Samza Job Package". As I am running off of >> the >> > > latest I try running gradle as specified: >> > > >> > > $ ./gradlew publishToMavenLocal >> > > >> > > FAILURE: Build failed with an exception. >> > > >> > > * What went wrong: >> > > Task 'publishToMavenLocal' not found in root project >> 'hello-samza'. >> > > >> > > * Try: >> > > Run gradlew tasks to get a list of available tasks. Run with >> > > --stacktrace option to get the stack trace. Run with >> > > --info >> > > >> > > or >> > > --debug >> > > option to get more log >> output. >> > > >> > > >> > > Then I saw that the bootstrap actually runs that so I thought I could >> > just >> > > move to the next step: >> > > >> > > $ mvn clean package >> > > >> > > Which, after a bunch of output, ultimately fails: >> > > >> > > [INFO] >> > > ------------------------------------------------------------ >> ------------ >> > > [INFO] BUILD FAILURE >> > > [INFO] >> > > ------------------------------------------------------------ >> ------------ >> > > [INFO] Total time: 7.819 s >> > > [INFO] Finished at: 2016-08-11T16:51:20-06:00 >> > > [INFO] Final Memory: 11M/151M >> > > [INFO] >> > > ------------------------------------------------------------ >> ------------ >> > > [ERROR] Failed to execute goal on project hello-samza: Could not >> > > resolve dependencies for project org.apache.samza:hello-samza: >> > jar:0.11.0: >> > > Failed to collect dependencies at >> > > org.apache.samza:samza-api:jar:0.11.0-SNAPSHOT: Failed to read >> artifact >> > > descriptor for org.apache.samza:samza-api:jar:0.11.0-SNAPSHOT: Could >> not >> > > transfer artifact org.apache.samza:samza-api:pom:0.11.0-SNAPSHOT >> from/to >> > > scala-tools.org (https://oss.sonatype.org/content/groups/scala-tools >> ): >> > > Access denied to: >> > > https://oss.sonatype.org/content/groups/scala-tools/ >> > > org/apache/samza/samza-api/0.11.0-SNAPSHOT/samza-api-0.11.0- >> SNAPSHOT.pom >> > > , ReasonPhrase:Forbidden. -> [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/ >> > > DependencyResolutionException >> > > >> > > >> > > I then ran it with the -X switch and see a bunch of these errors: >> > > >> > > org.eclipse.aether.transfer.MetadataTransferException: Could not >> > > transfer metadata >> > > org.apache.samza:samza-kafka_2.10:0.11.0-SNAPSHOT/maven-metadata.xml >> > > from/to scala-tools.org (https://oss.sonatype.org/ >> > > content/groups/scala-tools): >> > > Access denied to: >> > > https://oss.sonatype.org/content/groups/scala-tools/ >> > > org/apache/samza/samza-kafka_2.10/0.11.0-SNAPSHOT/maven-metadata.xml >> > > , ReasonPhrase:Forbidden. >> > > >> > > >> > > I'm not sure how to proceed from here. I know I have managed to get >> > > previous versions to work for me. Is it possibly related to a >> difference >> > > between linux (my previous env) and OS X (my current env)? >> > > >> > > Thanks, >> > > >> > > Ryan >> > > >> > >> > >
