Re: Different library versions (zkclient, metrics) referenced from build files?
This was mentioned a few weeks ago with the sbt-assembly task finding multiple versions of the same libs. The Build.scala was transposed from the older build, so I didn't see it at the time, but definitely the stuff in lib/ seems a bit sketchy if there are versions of those JARs in Maven Central (or other suitable repo). Derek On Fri, Mar 22, 2013 at 10:30 AM, Dragos Manolescu < dragos.manole...@servicenow.com> wrote: > Hi -- > > While working on publishing the kafka 0.8 JAR to our nexus server I > noticed that kafka/project/Build.scala and > kafka/project/build/KafkaProject.scala point to different library versions. > In KafkaProject.scala: > > > def zkClientDep = > > com.101tec > zkclient > 0.2 > compile > > > def metricsDepsCore = > > com.yammer.metrics > metrics-core > 3.0.0-SNAPSHOT > compile > > > def metricsDepsAnnotations = > > com.yammer.metrics > metrics-annotation > 3.0.0-SNAPSHOT > compile > > > While Build.scala references different versions (which reside in the local > lib folder): > > > // POM Tweaking for core: > def zkClientDep = > > zkclient > zkclient > 20120522 > compile > > > def metricsDeps = > > > com.yammer.metrics > metrics-core > 3.0.0-c0c8be71 > compile > > > com.yammer.metrics > metrics-annotations > 3.0.0-c0c8be71 > compile > > > > As there seem to be API differences between these different versions I am > wondering whether the different references are by design or they're > something that slipped through the cracks. Has anybody else ran into this? > > Thanks, > > -Dragos > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: EasyMock?
Let me go ahead and put in some time in next week to get it running again. I've only been skimming the emails lately, but is Kafka moved over to Git yet? Using Git would allow me to avoid some of the issues we ran into trying to submit an SVN patch due to deleted files, etc. Also, which branch/revision should I be targeting? Thanks, Derek On Wed, Dec 12, 2012 at 11:45 PM, Joe Stein wrote: > Hey Derek, I totally got swamped at work and didn't get a chance to bang on > the sbt change. > > I am not a sbt whiz you might be better to get this over the finish line is > it something you might be able to-do? > > if so I can review and commit, np > > IMHO 0.8 should not ship with out supporting latest sbt and scala in a good > way it is one thing I have heard time and again from Scala community folks > from perception, contributions, etc > > let me know if you don't have time I can figure some time to noodle and > bang away again at it last time I got it all down to one test failing but > some other tickets I should attend to also > > On Tue, Nov 20, 2012 at 4:21 PM, Derek Chen-Becker > wrote: > > > I haven't had any time to work on it in a few months, but it's definitely > > something I'd like to finish up. I think the last remaining issue is that > > SBT isn't integrated into the external packaging scripts, but otherwise > it > > should work. > > > > Derek > > > > On Mon, Nov 19, 2012 at 9:24 PM, Joe Stein wrote: > > > > > I have not tried the KAFKA-139 ticket yet for latest scala but will > give > > > that a try this week. Looks cool. > > > > > > On Mon, Nov 19, 2012 at 7:11 PM, Derek Chen-Becker > > > wrote: > > > > > > > In particular it breaks some tests between Scala 2.8.0 and 2.9.x due > to > > > > changes in Scala's collections impls that impact Map traversal > order. I > > > > haven't had any time to work further on the SBT cross-build/upgrade > > > ticket > > > > ( > > > > https://issues.apache.org/jira/browse/KAFKA-139), but that was > > > definitely > > > > a > > > > blocker. > > > > > > > > Derek > > > > > > > > On Mon, Nov 19, 2012 at 3:38 PM, Jay Kreps > > wrote: > > > > > > > > > What has people's experience with EasyMock been? > > > > > > > > > > I am really struggling with it. It seems to encourage reaching > inside > > > > > classes and programming an explicit list of calls they will make. > > This > > > > > makes the tests very fragile to internal changes. > > > > > > > > > > It also doesn't seem to play all that well with scala due to all > the > > > > > reflection. > > > > > > > > > > I was originally a big fan since it got us away from massive > > > > > non-deterministic integration tests. > > > > > > > > > > But I wonder if we wouldn't be better off just writing simple > > hand-made > > > > > mocks for major classes or increasing the quality of our test > > harnesses > > > > to > > > > > do integration testing...? > > > > > > > > > > Thoughts? > > > > > > > > > > -Jay > > > > > > > > > > > > > > > > > > > > > -- > > > > *Derek Chen-Becker* > > > > *Precog Lead Infrastructure Engineer* > > > > de...@precog.com > > > > 303-752-1700 > > > > > > > > > > > > > > > > -- > > > > > > /* > > > Joe Stein > > > http://www.linkedin.com/in/charmalloc > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > */ > > > > > > > > > > > -- > > *Derek Chen-Becker* > > *Precog Lead Infrastructure Engineer* > > de...@precog.com > > 303-752-1700 > > > > > > -- > > /* > Joe Stein > http://www.linkedin.com/in/charmalloc > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > */ > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: kafka repo moved to git
Awesome! I hope to have a pull request for updated SBT builds some time next week :) On Fri, Dec 14, 2012 at 12:50 PM, Jay Kreps wrote: > And as with apache svn, it sounds like you need to use https if you want a > writable version and http otherwise... > > -Jay > > > On Fri, Dec 14, 2012 at 10:43 AM, Jun Rao wrote: > > > Hi, Everyone, > > > > We have moved Kafka repo to git. The location of the new repo is at: > > https://git-wip-us.apache.org/repos/asf/kafka.git > > > > Please follow the following instruction on how to use it. > > > > https://git-wip-us.apache.org > > > > Thanks, > > > > Jun > > > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: EasyMock?
The bug bit me, so reapplied my patch on the latest from the 0.8 branch. I pushed it up to my Git repo: https://github.com/dchenbecker/kafka-sbt I got it back to the point where it compiles, tests, etc. The stumbling block last time was packaging, so there's still a fair bit of work to do there. I also ned to re-test cross builds with 2.9.1/2.9.2, since both of those had issues with EasyMock (fix in this patched version). If you have a github account I can add you to the repo if you want to use it as the workspace. I'm not an apache committer so I can't put a branch there. Derek On Wed, Dec 12, 2012 at 11:45 PM, Joe Stein wrote: > Hey Derek, I totally got swamped at work and didn't get a chance to bang on > the sbt change. > > I am not a sbt whiz you might be better to get this over the finish line is > it something you might be able to-do? > > if so I can review and commit, np > > IMHO 0.8 should not ship with out supporting latest sbt and scala in a good > way it is one thing I have heard time and again from Scala community folks > from perception, contributions, etc > > let me know if you don't have time I can figure some time to noodle and > bang away again at it last time I got it all down to one test failing but > some other tickets I should attend to also > > On Tue, Nov 20, 2012 at 4:21 PM, Derek Chen-Becker > wrote: > > > I haven't had any time to work on it in a few months, but it's definitely > > something I'd like to finish up. I think the last remaining issue is that > > SBT isn't integrated into the external packaging scripts, but otherwise > it > > should work. > > > > Derek > > > > On Mon, Nov 19, 2012 at 9:24 PM, Joe Stein wrote: > > > > > I have not tried the KAFKA-139 ticket yet for latest scala but will > give > > > that a try this week. Looks cool. > > > > > > On Mon, Nov 19, 2012 at 7:11 PM, Derek Chen-Becker > > > wrote: > > > > > > > In particular it breaks some tests between Scala 2.8.0 and 2.9.x due > to > > > > changes in Scala's collections impls that impact Map traversal > order. I > > > > haven't had any time to work further on the SBT cross-build/upgrade > > > ticket > > > > ( > > > > https://issues.apache.org/jira/browse/KAFKA-139), but that was > > > definitely > > > > a > > > > blocker. > > > > > > > > Derek > > > > > > > > On Mon, Nov 19, 2012 at 3:38 PM, Jay Kreps > > wrote: > > > > > > > > > What has people's experience with EasyMock been? > > > > > > > > > > I am really struggling with it. It seems to encourage reaching > inside > > > > > classes and programming an explicit list of calls they will make. > > This > > > > > makes the tests very fragile to internal changes. > > > > > > > > > > It also doesn't seem to play all that well with scala due to all > the > > > > > reflection. > > > > > > > > > > I was originally a big fan since it got us away from massive > > > > > non-deterministic integration tests. > > > > > > > > > > But I wonder if we wouldn't be better off just writing simple > > hand-made > > > > > mocks for major classes or increasing the quality of our test > > harnesses > > > > to > > > > > do integration testing...? > > > > > > > > > > Thoughts? > > > > > > > > > > -Jay > > > > > > > > > > > > > > > > > > > > > -- > > > > *Derek Chen-Becker* > > > > *Precog Lead Infrastructure Engineer* > > > > de...@precog.com > > > > 303-752-1700 > > > > > > > > > > > > > > > > -- > > > > > > /* > > > Joe Stein > > > http://www.linkedin.com/in/charmalloc > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > */ > > > > > > > > > > > -- > > *Derek Chen-Becker* > > *Precog Lead Infrastructure Engineer* > > de...@precog.com > > 303-752-1700 > > > > > > -- > > /* > Joe Stein > http://www.linkedin.com/in/charmalloc > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > */ > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: git workflow
; On Saturday, January 5, 2013, Joe Stein wrote: > >>> > >>> > I am getting the no email after doing > >>> > > >>> > git am --signoff < xyz.patch > >>> > > >>> > so nothing gets in to commit to set the author :( > >>> > > >>> > On Sat, Jan 5, 2013 at 12:30 AM, Jay Kreps >>> > > >>> > wrote: > >>> > > >>> > > I have but I don't really know why. This format worked for me: > >>> > > git commit --author='Bertrand Russell >>> > >>> > >' > >>> > > > >>> > > > >>> > > On Fri, Jan 4, 2013 at 8:35 PM, Joe Stein >>> > > >>> > wrote: > >>> > > > >>> > > > I started following this so far really helpful thanks!! > >>> > > > > >>> > > > Running into some issues reviewing someone's patch getting "Patch > >>> does > >>> > > not > >>> > > > have a valid e-mail address." googling to figure out what is > wrong > >>> > > figure I > >>> > > > mention here if anyone bumped into this yet > >>> > > > > >>> > > > thnx > >>> > > > > >>> > > > On Thu, Jan 3, 2013 at 11:17 AM, Jun Rao >>> > > >>> > wrote: > >>> > > > > >>> > > > > Thanks for documenting this. Could you also add how to resolve > >>> > > conflicts > >>> > > > > during rebase? > >>> > > > > > >>> > > > > Jun > >>> > > > > > >>> > > > > On Wed, Jan 2, 2013 at 1:45 PM, Jay Kreps >>> > > >>> > wrote: > >>> > > > > > >>> > > > > > I don't know about other people but I find git kind of > >>> confusing. I > >>> > > > > thought > >>> > > > > > it would be useful to try to document the normal workflow for > >>> > > different > >>> > > > > use > >>> > > > > > cases: > >>> > > > > > 1. Contributing a patch > >>> > > > > > 2. Reviewing and integrating a patch that is contributed > >>> > > > > > 3. Doing development as a committer > >>> > > > > > 4. Keeping a copy of your local work on github (since it > >>> doesn't > >>> > seem > >>> > > > > > Apache has a place to keep local backups of work in > progress). > >>> > > > > > > >>> > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow > >>> > > > > > > >>> > > > > > I would like to link this up from the contributor page to > help > >>> > people > >>> > > > > > (including my future self). Objections? > >>> > > > > > > >>> > > > > > I am not a git expert, so any feedback to improve these > >>> recipes or > >>> > > bug > >>> > > > > > fixes (since I haven't tried everything) would be very much > >>> > > > appreciated. > >>> > > > > If > >>> > > > > > you are about to do one of the above things, try the recipe > >>> and see > >>> > > if > >>> > > > it > >>> > > > > > can be improved. > >>> > > > > > > >>> > > > > > Cheers, > >>> > > > > > > >>> > > > > > -Jay > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > -- > >>> > > > > >>> > > > /* > >>> > > > Joe Stein > >>> > > > http://www.linkedin.com/in/charmalloc > >>> > > > Twitter: @allthingshadoop < > http://www.twitter.com/allthingshadoop> > >>> > > > */ > >>> > > > > >>> > > > >>> > > >>> > > >>> > > >>> > -- > >>> > > >>> > /* > >>> > Joe Stein > >>> > http://www.linkedin.com/in/charmalloc > >>> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > >>> > */ > >>> > > >>> > >>> > >>> -- > >>> David Arthur > >>> > >> > >> > >> > >> -- > >> > >> /* > >> Joe Stein > >> http://www.linkedin.com/in/charmalloc > >> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > >> */ > >> > > > > > > > > -- > > > > /* > > Joe Stein > > http://www.linkedin.com/in/charmalloc > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > */ > > > > > > -- > > /* > Joe Stein > http://www.linkedin.com/in/charmalloc > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > */ > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: git workflow
It makes it easier for a non-committer to contribute via email, but with publicly available repos (a la GitHub) it's just as easy to merge from a remote (and doesn't require contorting through hoops for certain scenarios). On Jan 7, 2013 7:45 AM, "David Arthur" wrote: > Diff/patch makes it easy for non-committer to contribute. > > On 1/7/13 12:52 AM, Derek Chen-Becker wrote: > >> Although I haven't contributed much here yet, I did want to ask: why >> diff/patch and not pull/merge? I know my work on getting the SBT build >> working with a modern SBT was quite a headache for everyone because the >> diff format was unable to convey things like "delete this binary file and >> add this other one". >> >> Derek >> >> >> On Sat, Jan 5, 2013 at 10:35 PM, Joe Stein wrote: >> >> ok with some more research today it seems the difference and issues I was >>> having was from the patch being made with >>> >>> git diff vs git format-patch >>> >>> with git diff (which is how the patch I was reviewing was made) you apply >>> doing "patch -p1 < patch" >>> >>> no commits messages are preserved with git diff. I think there are pros >>> and cons to this. >>> >>> If folks make good commit messages then this is great however I prefer >>> the >>> git diff patch myself from contribs because then I can commit with a >>> message for the JIRA ticket and the reviewer >>> >>> thoughts on git diff vs git format-patch ? >>> >>> I updated the wiki to deal with the error i encountered since it already >>> references format-patch I but think we should have some consensus for >>> contributors and how they should proceed and how we should too. >>> >>> On Sat, Jan 5, 2013 at 2:02 PM, Joe Stein wrote: >>> >>> Ok, I figured out the problem. The problem was with the patch format so >>>> >>> I >>> >>>> will take care of that ... the patch is minor enough I will take the >>>> code >>>> changes and whip up a new patch and let Maxime know (assuming that patch >>>> >>> is >>> >>>> good) about how to make a Kafka patch moving forward). >>>> >>>> I noticed the incubation URL was wrong on the README so I walked through >>>> the contributor steps and everything worked just perfectly >>>> >>>> the only thing I did notice is that the commit message I put in "as a >>>> contributor" was part of the patch and everything so I think we should >>>> >>> call >>> >>>> out some guidelines for making commit messages, like always put the >>>> KAFKA-XYZ in the message so when we review and push everything goes in >>>> >>> how >>> >>>> we expected if we made the change and committed ourselves. >>>> >>>> I just could not let it go, now I am going to-do what I need to for work >>>> before my daughter wakes up =8^) >>>> >>>> >>>> On Sat, Jan 5, 2013 at 1:42 PM, Joe Stein wrote: >>>> >>>> that did not work either >>>>> >>>>> I can't even get the patch to apply from the latest trunk because of >>>>> >>>> this >>> >>>> message of patch without email >>>>> >>>>> so the patch is here >>>>> >>>>> https://issues.apache.org/**jira/secure/attachment/** >>> 12563266/KAFKA-133.patch<https://issues.apache.org/jira/secure/attachment/12563266/KAFKA-133.patch> >>> >>>> I go through the steps on the git workflow >>>>> >>>>> git clone >>>>> https://git-wip-us.apache.org/**repos/asf/kafka.git<https://git-wip-us.apache.org/repos/asf/kafka.git>kafka >>>>> cd kafka >>>>> git fetch >>>>> git checkout trunk >>>>> //already on trunk >>>>> git apply --stat ../KAFKA-133.patch >>>>> //project/build.properties |2 +- >>>>> //project/build/KafkaProject.**scala | 44 >>>>> +-** >>>>> //2 files changed, 25 insertions(+), 21 deletions(-) >>>>> git apply --check ../KAFKA-133.patch >>>>> git am --signoff < ../KAFKA-133.patch >>>>> //Patch does not have a valid e-mail address. >>>>> >>>>> my git --
Re: git workflow
If it's mandated by Apache rules, I understand, but I do think that GitHub/git provide improved workflow over SVN + patch. Apache appears to be mirroring to GitHub anyway: https://github.com/apache/kafka You even have a pull request (5 months old) already. Things like pull request review/commenting, as mentioned, are very nice, and it would be a shame to not be able to use them. Derek On Mon, Jan 7, 2013 at 9:06 AM, Jay Kreps wrote: > The reason we take diffs is because traditionally the mandatory Apache > toolchain is svn+jira+patch/diff. When we were on github of course we used > that. > > I'm actually not sure of the Apache rules here. Can we just directly accept > github pull requests? I.e. you fork the apache mirror and send a pull > request? Github has lots of tools for seeing diffs, commenting on code, etc > so this would be fantastic. Is that considered bad form? We could just have > the JIRA point to the github url... > > -Jay > > > On Mon, Jan 7, 2013 at 7:05 AM, Derek Chen-Becker > wrote: > > > It makes it easier for a non-committer to contribute via email, but with > > publicly available repos (a la GitHub) it's just as easy to merge from a > > remote (and doesn't require contorting through hoops for certain > > scenarios). > > On Jan 7, 2013 7:45 AM, "David Arthur" wrote: > > > > > Diff/patch makes it easy for non-committer to contribute. > > > > > > On 1/7/13 12:52 AM, Derek Chen-Becker wrote: > > > > > >> Although I haven't contributed much here yet, I did want to ask: why > > >> diff/patch and not pull/merge? I know my work on getting the SBT build > > >> working with a modern SBT was quite a headache for everyone because > the > > >> diff format was unable to convey things like "delete this binary file > > and > > >> add this other one". > > >> > > >> Derek > > >> > > >> > > >> On Sat, Jan 5, 2013 at 10:35 PM, Joe Stein > wrote: > > >> > > >> ok with some more research today it seems the difference and issues I > > was > > >>> having was from the patch being made with > > >>> > > >>> git diff vs git format-patch > > >>> > > >>> with git diff (which is how the patch I was reviewing was made) you > > apply > > >>> doing "patch -p1 < patch" > > >>> > > >>> no commits messages are preserved with git diff. I think there are > > pros > > >>> and cons to this. > > >>> > > >>> If folks make good commit messages then this is great however I > prefer > > >>> the > > >>> git diff patch myself from contribs because then I can commit with a > > >>> message for the JIRA ticket and the reviewer > > >>> > > >>> thoughts on git diff vs git format-patch ? > > >>> > > >>> I updated the wiki to deal with the error i encountered since it > > already > > >>> references format-patch I but think we should have some consensus for > > >>> contributors and how they should proceed and how we should too. > > >>> > > >>> On Sat, Jan 5, 2013 at 2:02 PM, Joe Stein > wrote: > > >>> > > >>> Ok, I figured out the problem. The problem was with the patch > format > > so > > >>>> > > >>> I > > >>> > > >>>> will take care of that ... the patch is minor enough I will take the > > >>>> code > > >>>> changes and whip up a new patch and let Maxime know (assuming that > > patch > > >>>> > > >>> is > > >>> > > >>>> good) about how to make a Kafka patch moving forward). > > >>>> > > >>>> I noticed the incubation URL was wrong on the README so I walked > > through > > >>>> the contributor steps and everything worked just perfectly > > >>>> > > >>>> the only thing I did notice is that the commit message I put in "as > a > > >>>> contributor" was part of the patch and everything so I think we > should > > >>>> > > >>> call > > >>> > > >>>> out some guidelines for making commit messages, like always put the > > >>>> KAFKA-XYZ in the message so when we review and push everything goes > in > > >>>&g
Re: 0.8 build problems
The two simplest approaches (short of parsing SBT output for classpaths) would be to either use https://github.com/n8han/conscript or https://github.com/sbt/sbt-assembly. Assembly would give you a nice, self-contained JAR with all deps. Conscript essentially uses SBT to fetch deps and run. I'm more familiar with assembly, so I'd be happy to add it to the build (it's pretty trivial). Derek On Thu, Feb 21, 2013 at 3:40 PM, David Arthur wrote: > I'm having trouble building the project with sbt, specifically I am unable > to run package and have the kafka-server-start.sh script work > > git clone > git://github.com/apache/kafka.**git<http://github.com/apache/kafka.git> > ./sbt update > ./sbt "++2.8.0 package" > ./bin/kafka-server-start.sh config/server.properties > > Exception in thread "main" java.lang.**NoClassDefFoundError: > scala/ScalaObject > at java.lang.ClassLoader.**defineClass1(Native Method) > at java.lang.ClassLoader.**defineClassCond(ClassLoader.**java:631) > at java.lang.ClassLoader.**defineClass(ClassLoader.java:**615) > at java.security.**SecureClassLoader.defineClass(** > SecureClassLoader.java:141) > at java.net.URLClassLoader.**defineClass(URLClassLoader.**java:283) > at java.net.URLClassLoader.**access$000(URLClassLoader.**java:58) > at java.net.URLClassLoader$1.run(**URLClassLoader.java:197) > at java.security.**AccessController.doPrivileged(**Native Method) > at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > at java.lang.ClassLoader.**defineClass1(Native Method) > at java.lang.ClassLoader.**defineClassCond(ClassLoader.**java:631) > at java.lang.ClassLoader.**defineClass(ClassLoader.java:**615) > at java.security.**SecureClassLoader.defineClass(** > SecureClassLoader.java:141) > at java.net.URLClassLoader.**defineClass(URLClassLoader.**java:283) > at java.net.URLClassLoader.**access$000(URLClassLoader.**java:58) > at java.net.URLClassLoader$1.run(**URLClassLoader.java:197) > at java.security.**AccessController.doPrivileged(**Native Method) > at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > at kafka.Kafka.main(Kafka.scala) > Caused by: java.lang.**ClassNotFoundException: scala.ScalaObject > at java.net.URLClassLoader$1.run(**URLClassLoader.java:202) > at java.security.**AccessController.doPrivileged(**Native Method) > at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > ... 25 more > > I have tried manually building a classpath and running java directly, but > then it complains about missing slf4j. The only way I've been able to run > Kafka is through sbt interactively with the "run" task (I noticed in this > case it's picking up slf4j from ~/.ivy/cache). > > Any advise? > > -David > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
Re: 0.8 build problems
Reviewed. I added my comments on the ticket. Thanks! On Thu, Feb 21, 2013 at 5:03 PM, Swapnil Ghike wrote: > Hi Derek, > > We probably have a patch for adding assembly at > https://issues.apache.org/jira/browse/KAFKA-733. Can you review it? > > Thanks, > Swapnil > > On 2/21/13 2:46 PM, "Derek Chen-Becker" wrote: > > >The two simplest approaches (short of parsing SBT output for classpaths) > >would be to either use https://github.com/n8han/conscript or > >https://github.com/sbt/sbt-assembly. Assembly would give you a nice, > >self-contained JAR with all deps. Conscript essentially uses SBT to fetch > >deps and run. I'm more familiar with assembly, so I'd be happy to add it > >to > >the build (it's pretty trivial). > > > >Derek > > > > > >On Thu, Feb 21, 2013 at 3:40 PM, David Arthur wrote: > > > >> I'm having trouble building the project with sbt, specifically I am > >>unable > >> to run package and have the kafka-server-start.sh script work > >> > >> git clone > >>git://github.com/apache/kafka.**git<http://github.com/apache/kafka.git> > >> ./sbt update > >> ./sbt "++2.8.0 package" > >> ./bin/kafka-server-start.sh config/server.properties > >> > >> Exception in thread "main" java.lang.**NoClassDefFoundError: > >> scala/ScalaObject > >> at java.lang.ClassLoader.**defineClass1(Native Method) > >> at java.lang.ClassLoader.**defineClassCond(ClassLoader.**java:631) > >> at java.lang.ClassLoader.**defineClass(ClassLoader.java:**615) > >> at java.security.**SecureClassLoader.defineClass(** > >> SecureClassLoader.java:141) > >> at java.net.URLClassLoader.**defineClass(URLClassLoader.**java:283) > >> at java.net.URLClassLoader.**access$000(URLClassLoader.**java:58) > >> at java.net.URLClassLoader$1.run(**URLClassLoader.java:197) > >> at java.security.**AccessController.doPrivileged(**Native Method) > >> at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > >> at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > >> at java.lang.ClassLoader.**defineClass1(Native Method) > >> at java.lang.ClassLoader.**defineClassCond(ClassLoader.**java:631) > >> at java.lang.ClassLoader.**defineClass(ClassLoader.java:**615) > >> at java.security.**SecureClassLoader.defineClass(** > >> SecureClassLoader.java:141) > >> at java.net.URLClassLoader.**defineClass(URLClassLoader.**java:283) > >> at java.net.URLClassLoader.**access$000(URLClassLoader.**java:58) > >> at java.net.URLClassLoader$1.run(**URLClassLoader.java:197) > >> at java.security.**AccessController.doPrivileged(**Native Method) > >> at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > >> at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > >> at kafka.Kafka.main(Kafka.scala) > >> Caused by: java.lang.**ClassNotFoundException: scala.ScalaObject > >> at java.net.URLClassLoader$1.run(**URLClassLoader.java:202) > >> at java.security.**AccessController.doPrivileged(**Native Method) > >> at java.net.URLClassLoader.**findClass(URLClassLoader.java:**190) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**306) > >> at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:301) > >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**247) > >> ... 25 more > >> > >> I have tried manually building a classpath and running java directly, > >>but > >> then it complains about missing slf4j. The only way I've been able to > >>run > >> Kafka is through sbt interactively with the "run" task (I noticed in > >>this > >> case it's picking up slf4j from ~/.ivy/cache). > >> > >> Any advise? > >> > >> -David > >> > > > > > > > >-- > >*Derek Chen-Becker* > >*Precog Lead Infrastructure Engineer* > >de...@precog.com > >303-752-1700 > > -- *Derek Chen-Becker* *Precog Lead Infrastructure Engineer* de...@precog.com 303-752-1700
