Well, thank you for the pointer but the result is less than desirable. I decided not to waste my time and count the unnumbered steps, after I got past 3.
The Rule of the Trinity: there should be no more than 3 simple steps to build a functioning foundation or survive failure or establish principles to live life by, which is really only the first 2 restated.
Is there nascent maven support to let me d/l eclipse, d/l kafka, mvn eclipse:eclipse, then import the project into eclipse...I call that 3 steps, since I already have step 0: eclipse. eclipse, eclipse, eclispe... :)
From: Andrea Gazzarini Sent: Saturday, May 11, 2013 12:15 PM To: [EMAIL PROTECTED] Subject: Re: eclipse project/classpath files for 0.8?
Ahh, yes, Andrea - it was you who suggested to me to use the sbt plugin approach. I finally got around to it and this worked perfectly the first time, other than the scala unit tests. Thanks very much for explaining it to me.
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project 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