Jun, I have opened a ticket targeting 0.9
https://issues.apache.org/jira/browse/KAFKA-855
-David
On 4/8/13 1:06 AM, Jun Rao wrote:
David,
We'd be open to a new build tool if SBT is deemed too hard to use. We can
revisit this post 0.8. Do you want to open a jira to track this?
Thanks,
Jun
On Fri, Apr 5, 2013 at 12:55 PM, David Arthur <mum...@gmail.com> wrote:
After getting frustrated with SBT, and being unable to figure out
seemingly simple problems like KAFKA-843, I decided to try something
completely different.
I spent some time yesterday adapting some Ant/Ivy boilerplate I use for
projects to Kafka. It was actually pretty easy to get working (Kafka is a
very simple build), and I think it's _much_ cleaner than the existing SBT
stuff.
Attached is a patchset of the work I did. N.B., this is totally
experimental and only considers the "core" part of the project.
At this point I can:
* Resolve all deps through Ivy (except yammer.metrics which is checked in)
* Resolve different versions of Scala through Ivy (i.e., cross
compile-ability)
* Compile the source
* Run all the unit tests (all passing)
* Compile a jar
* Package a tarball of the libs, conf, and bin scripts
Since all the libraries are localized to the project (and not in ~/.ivy2),
the packaging is trivial. Also, the bin scripts could be cleaned up
significantly (which they need to be IMO).
I would love to hear what everyone thinks of this. Am I crazy? Is SBT
really better? Convince me!
-David
