We are trying to create an ant build for legacy code, that is build using some make tool, as I don't want to break the already complicated buiild, I preferred simulate the same behaviour as the make tool we're using. As that legacy code is still alive I cannot count the files and decide how to split because it could break in several months. Jean
Phil Weighill Smith <[EMAIL PROTECTED]> wrote: Why not simply put two calls to javac in your build script and split the source tree in two in the same way that you have in your new task, passing one tree to the first call and the other to the second? Clearly you need to ensure that the first call compiles "pre-requisite" code for the second call and that you should avoid cyclic references between the two sets of classes. Phil :n. PS: I would consider re-structuring the application into "subsystems" with separate source trees and separate build scripts per subsystem. Dependencies between subsystems only on the class files (not the source files). This is the approach we have taken to great effect. On Tue, 2005-07-12 at 00:12 -0700, Jean Lazarou wrote: > We had problem with a (legacy) build from scratch, seems that, because we > have too many java files to compile, nothing is compiled (both on Linux and > Windows2000). > > After spending 4 days on that, I decided to split the compilation, I created > a new task, name "bydir-javac". The task is derived from Javac. > > Can I publish this? Is it a better way of doing it? > > Jean Lazarou > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
