Another fix would be to add build/ivy/jars/common to the classpath; that's the direction I was thinking to go.
Comments? On Mon, Apr 6, 2009 at 10:55 PM, Eric Yang <[email protected]> wrote: > The jar files are only packaged to lib for tarball or rpm packages. > Chukwa would not run from the source tree currently, but it should run from > binary package. Some minor adjustment in build.xml could make the > downloaded to ivy jar files directly to lib, and have chukwa run from the > source tree. +1 to add capability to run from source tree. > > I also branched for chukwa-0.1. Please check out the code from: > > https://svn.apache.org/repos/asf/hadoop/chukwa/branches/chukwa-0.1 > > When it is ready, we will tag for chukwa-0.1.2. > > Regards, > Eric > > On 4/6/09 10:17 PM, "Ariel Rabkin" <[email protected]> wrote: > >> Hey folks. >> >> the jars from Ivy don't seem to ever get included on the classpath >> when you start chukwa processes at the command line. What gives? >> >> --Ari > > -- Ari Rabkin [email protected] UC Berkeley Computer Science Department
