*1) Unit tests* Within an Eclipse workspace created using the first approach (i.e. Eclipse without sbt plugin) I have a failure:
kafka.log.LogTest.testTimeBasedLogRoll(kafka.log.LogTest) junit.framework.AssertionFailedError: There should still be exactly one segment. expected:<1> but was:<2> at junit.framework.Assert.fail(Assert.java:47) ... at kafka.log.LogTest.testTimeBasedLogRoll(LogTest.scala:80) ...
and an error
kafka.producer.AsyncProducerTest.testFailedSendRetryLogic(kafka.producer.AsyncProducerTest) kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries. at kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:88) at kafka.producer.AsyncProducerTest.testFailedSendRetryLogic(AsyncProducerTest.scala:439) ...
The other 158 tests are OK.
*2) Source folders* Using the second approach (Eclipse with sbt plugin), the sbt plugin creates Eclipse projects with default source folders. For core module this is not ok because tests are in test/unit and test/other. I suppose the core/build.sbt needs to be changed.
*3) Intellij**IDEA * At the moment I don't have Intellij installed on my laptop so I left the content of this section ontouched.
Thanks. The unit test failure that you saw is transient.
Jun On Fri, May 10, 2013 at 9:56 AM, Andrea Gazzarini < [EMAIL PROTECTED]> wrote:
Jun Rao 2013-05-11, 05:01
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext