By the way, if you are working on the standalone version of jetty, maybe you could enhance the build script to create a new distributable binary? Not necessary, but I would like to make it an option in the 1.1 release.
-Kevin -----Original Message----- From: Kevin Ross [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 1:13 PM To: [EMAIL PROTECTED] Subject: RE: xindice.bat / xindice.sh scripts broken in CVS ? Aadi, if you find anything wrong and want to fix it, GREAT! Just file the bug under 1.1 and include the patch. I'll review it ASAP. -Kevin -----Original Message----- From: Mailing Lists (Aadi) [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 11:01 AM To: [EMAIL PROTECTED] Subject: Re: xindice.bat / xindice.sh scripts broken in CVS ? Vladimir R. Bossicard wrote: >>i found a number of issues, but the key one preventing me from starting >>the server is : >> >> > >0) please note EVERY issue you found, not only the more severe ones. > absolutely. i just wanted to get to a reasonable stopping point before i listed issues and submitted patches. > >1) Should I define a new "release" bugzilla category to order these bugs? > i don't know much about how apache works, but shouldn't we be tagging issues against a milestone? > >2) Kevin, [without lecturing you] I would create nightly releases (simply put >them into your cvs.apache account, no need to advertise them). It's very likely >that the first releases will not work and having multiple releases gives plenty >of time to spot/fix the problems. > >3) How can a user migrate the data/indexes from 1.0 to 1.1? Are the tbls >compatible? I don't know if this is an issue and it's maybe trivial, but I >haven't seen any documentation on this topic. > >-Vladimir > > > thanks in advance, -a
