> -----Original Message----- > From: Eugene Bekker [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 11, 2000 5:56 PM > To: [EMAIL PROTECTED] > Subject: Re: Patch: JAVAC dependency tracking and multiple src paths handling > > > > > Conor MacNeill wrote: > > > > For multiple source paths, I submitted a patch for multiple source paths a > > while back. I chose to use a comma to separate the source paths since it > > seemed likely to offend the Windows folks and the Unix folks equally :-) The > > patch was not applied because of the use of that comma. There was also some > > desire to support elements instead of just an attribute, something like > > <javac> > > <srcdir name="xyz"> > > <srcdir name="abc"> > > </javac> > > I think something along these lines is probably the cleanest/safest > approach. But does Ant support nested elements within tasks? Perhaps not > yet... Another solution is to list the files out in a separate file (like > java.lst) separated by newlines. Then simply have some sort of an include > reference. Although \n is a legal filename character in Unix it's probably > unlikely to be big problem. And if it is, the Properties class provides a > way of escaping any characters. > > > > > I also only follow direct relationships. Say you have a scenario of A > > depends on B and B depends on C but A does not depend on C. If you change C, > > my approach will only compile C and B but not A. My feeling is that if A > > does not depend directly on C, changes to C cannot affect A through B. I'm > > still thinking about that :-) > > But since modifying C, would recompile B, wouldn't A be recompiled since it > depends on B?
No. Class A directly depends on B and uses only B interfaces (here under interface I mean public variables and functions), which didn't change. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
