[
https://issues.apache.org/jira/browse/FLUME-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494511#comment-13494511
]
Hudson commented on FLUME-1690:
-------------------------------
Integrated in flume-trunk #323 (See
[https://builds.apache.org/job/flume-trunk/323/])
FLUME-1690: Elastic Search Sink doesn't run it's unit tests (Revision
107875af508541ab73311c875b6043b2eeab2da3)
Result = SUCCESS
brock :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=107875af508541ab73311c875b6043b2eeab2da3
Files :
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchDynamicSerializer.java
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchDynamicSerializerTest.java
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchLogStashEventSerializer.java
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/TestElasticSearchSink.java
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchSinkTest.java
*
flume-ng-sinks/flume-ng-elasticsearch-sink/src/test/java/org/apache/flume/sink/elasticsearch/ElasticSearchLogStashEventSerializerTest.java
> Elastic Search Sink doesn't run it's unit tests
> -----------------------------------------------
>
> Key: FLUME-1690
> URL: https://issues.apache.org/jira/browse/FLUME-1690
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: wolfgang hoschek
> Assignee: Hari Shreedharan
> Fix For: v1.3.0
>
> Attachments: FLUME-1690.patch
>
>
> I noticed that Elastic Search Sink doesn't run it's unit tests because they
> end with *Test rather than start with Test*. It's because top level pom
> defines this:
> <test.include.pattern>**/Test*.java</test.include.pattern>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
