The ant build file is currently designed for a full build process. It does lots of extra stuff as a result. I never really got around to making some convenient developer targets, but it would not be hard to do.
The problem is the code is separated into different areas, and the build process tries to preserve it. But there are still dependencies, so it's a little mixed up. Developer targets could just ignore the organization of the code and compile everything once and together, make just one jar file. This would speed development efforts. Then, when it's time to do a real binary build for release, the other process can be used. Get familiar with ant. It's really great. and super easy. -Mike On 10 Dec 2002 at 17:07, Jordi Salvat i Alabart wrote: > I'm not that familiar with ant... > > Q1: How do I do an incremental build during development? > > Q2: Isn't build.xml compiling each file twice, one in compile_all, one > in the corresponding compile_X? > > Yes, I'm being lazy here, but I'm in the process of building a > much-requested enhancement (or trying to) and this is getting much in my > way. > > Thanks, > > Jordi. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
