This is an automated email from the ASF dual-hosted git repository.

sblackmon pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/streams.git.


    from c4637f9  Merge pull request #411 from steveblackmon/STREAMS-556
     add 83e3213  STREAMS-566: Twitter: ThirtyDaySearchProvider
     new 3700a9b  Merge pull request #412 from steveblackmon/STREAMS-566

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../streams/twitter/api/ThirtyDaySearch.java       |  2 +-
 ...hProvider.java => ThirtyDaySearchProvider.java} | 36 ++++++++++------------
 ...rTask.java => ThirtyDaySearchProviderTask.java} | 34 ++++++++++----------
 .../SevenDaySearchProviderConfiguration.json       |  2 +-
 ...n => ThirtyDaySearchProviderConfiguration.json} | 12 ++++----
 ....java => TwitterThirtyDaySearchProviderIT.java} | 23 ++++++++------
 ....conf => TwitterThirtyDaySearchProviderIT.conf} |  8 ++---
 7 files changed, 59 insertions(+), 58 deletions(-)
 copy 
streams-contrib/streams-provider-twitter/src/main/java/org/apache/streams/twitter/provider/{SevenDaySearchProvider.java
 => ThirtyDaySearchProvider.java} (87%)
 copy 
streams-contrib/streams-provider-twitter/src/main/java/org/apache/streams/twitter/provider/{TwitterTimelineProviderTask.java
 => ThirtyDaySearchProviderTask.java} (74%)
 copy 
streams-contrib/streams-provider-twitter/src/main/jsonschema/org/apache/streams/twitter/config/{SevenDaySearchProviderConfiguration.json
 => ThirtyDaySearchProviderConfiguration.json} (62%)
 copy 
streams-contrib/streams-provider-twitter/src/test/java/org/apache/streams/twitter/test/providers/{TwitterTimelineProviderIT.java
 => TwitterThirtyDaySearchProviderIT.java} (70%)
 copy 
streams-contrib/streams-provider-twitter/src/test/resources/{TwitterIT.conf => 
TwitterThirtyDaySearchProviderIT.conf} (92%)

-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to