[
https://issues.apache.org/jira/browse/S4-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207621#comment-13207621
]
Mariano Valles commented on S4-16:
----------------------------------
Even though the problem has been solved in:
https://github.com/s4/twittertopiccount/commit/0302c0411131a7aae7dfe059b90c7f4fe3e68737
The documentation in [Set up the example
application|http://docs.s4.io/tutorials/getting_started.html#set-up-the-example-application]
requires to checkout tag v0.3.0 which does not include the above mentioned
commit.
The easiest way to solve this is to remove the
{{git checkout tags/v0.3.0}}
line from [Set up the example
application|http://docs.s4.io/tutorials/getting_started.html#set-up-the-example-application],
so that once cloned, the example is using the latest https authentication
method.
Another way is to include the mentioned commit in the v0.3.1 tag of the example
twitter app and then changing the command to {{git checkout tags/v0.3.1}}
> need to fix twitter authentication scheme in example
> ----------------------------------------------------
>
> Key: S4-16
> URL: https://issues.apache.org/jira/browse/S4-16
> Project: Apache S4
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Matthieu Morel
> Fix For: 0.4
>
>
> Twitter has changed its authentication scheme. As a consequence, our twitter
> feed example is currently broken.
> We need to modify the TwitterFeedListener class accordingly. Change should be
> trivial.
> see http://groups.google.com/group/s4-project/t/73fe1f3f003d150d
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
