On Mon, Apr 28, 2008 at 6:11 AM, Alexei Fedotov <[EMAIL PROTECTED]> wrote:
> Hello, Nathan, > Your sequence is a pretty robust one. I believe that things are enough Apparently not, since it fails to work. :) > > and limit myself to fewer commands: > > * check out top-level trunk > * ant -Dauto.fetch=true -Dhy.cfg=debug all > * do some class library hacking > * ant -Dbuild.module="archive" -Dhy.jdk="<dir>/trunk/target/hdk/jdk/" > test > (runs tests and regenerates hdk from the target dir which is used by > my debugger) Does this actually update the libraries in the "hy.jdk" path? What's the difference between 'hy.jdk' and 'hy.hdk'? Why do we have both? > > > Thanks! > > On Sat, Apr 26, 2008 at 6:46 AM, Nathan Beyer <[EMAIL > PROTECTED]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]>> > wrote: > > I've started a fresh workspace on an Ubuntu box and here's what I'm > doing. > > > > * check out top-level trunk > > * ant populate-source > > * ant -Dhy.cfg=debug build > > * rm -rf working_classlib/deploy/* > > * cp -r targert/hdk/* working_classlib/deploy/* > > * cd working_classlib > > * deploy/jdk/jre/bin/java -version > > Prints version information - works just fine > > * ant test > > class library tests run as expected > > * do some class library hacking > > * ant build > > * deploy/jdk/jre/bin/java -version > > does nothing, just waits, no output > > > > Shouldn't this work? How are other people doing class library > development > > and continuous rebuilds? I get the same results on Windows. > > > > -Nathan > > > > > > -- > With best regards, > Alexei >
