[
https://issues.apache.org/jira/browse/SAMZA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419314#comment-15419314
]
Jake Maes commented on SAMZA-1000:
----------------------------------
After talking with [~nickpan47] and [~navina], it looks like we need a couple
documentation updates.
1. Update the hello-samza tutorial in the master branch to NOT specify ```git
checkout latest```
2. Update the hello-samza tutorial in the release branch to specify the 10.1
tgz file
Details:
The hello-samza tutorial has a confusing part. It instructs the user to run
```git checkout latest``` as a mandatory step and then later says "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:" which sounds optional.
Since we don't publish nightly builds to a public *-SNAPSHOT version, you must
publish from a local copy of samza to produce the SNAPSHOT version.
There are a few ways to fix this:
1. Implement nightly builds so the SNAPSHOT version is available in maven
central. Then users can depend on it, or publish their own version to maven
local, but the commands in the tutorial always work.
2. We could merge hello-samza to be a sub module of samza so they are always
consistent. This ultimately will be our direction.
3. We should not make the ```git checkout latest``` a mandatory step. The
tutorial then defaults to the release version and users who want to work with a
local version have to publish to maven local and edit the pom.xml to point to
that version. This will be the short term fix.
> Hello-samza latest is broken after Samza 10.1 release
> -----------------------------------------------------
>
> Key: SAMZA-1000
> URL: https://issues.apache.org/jira/browse/SAMZA-1000
> Project: Samza
> Issue Type: Bug
> Reporter: Jake Maes
>
> After the samza 10.1 release, the hello-samza latest branch was updated to
> point to samza 0.11.0-SNAPSHOT. However, when running ```mvn clean package```
> it now produces the error below. I edited the pom.xml to point to
> 0.10.1-SNAPSHOT and that works fine, so I suspect that there is a problem
> with the 11.0 SNAPSHOT in maven. [~nickpan47] any thoughts?
> Error:
> [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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
