Yea, that fixed the problem. Thanks, Chris
On Wed, Apr 14, 2010 at 2:11 PM, Chad Berkley <berkley at nceas.ucsb.edu> wrote: > Ahh, yeah, I don't think that will work because that classpath is just for > the launcher. ?When the launcher gets called, it builds the runtime > classpath for Kepler then. ?I think what you should do is just put your jar > file into any module/lib/jar directory and it should get picked up by the > classpath builder at runtime. ?Let me know if that doesn't work. > > chad > > > Chris Weed wrote: >> >> I just added the jar I built to the classpath argument in the kepler.sh >> script. >> Chris >> >> On Wed, Apr 14, 2010 at 1:11 PM, Chad Berkley <berkley at nceas.ucsb.edu> >> wrote: >>> >>> Hi Chris, >>> >>> How are you launching Kepler? ?With ant or are you using one of the >>> installer versions? ?Where are you modifying the classpath? >>> >>> chad >>> >>> >>> Chris Weed wrote: >>>> >>>> Hi, >>>> I've been building Kepler from source in Eclipse, and I have no >>>> problem instantiating actors I have built in to the executable. >>>> I am now trying to instantiate them from the Kepler 2.0. >>>> I've tried Exporting a jar with the class for my actor, and then >>>> pointing the classpath to this location when I start Kepler. >>>> Unfortunately, when I then try to instantiate my actor, I just get >>>> java.lang.NoClassDefFoundError. >>>> I am curious why this doesn't work, and what is the preferred way to >>>> get my actors into Kepler. >>>> Chris >>>> _______________________________________________ >>>> Kepler-users mailing list >>>> Kepler-users at kepler-project.org >>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users >
