> From: Conor MacNeill [mailto:[EMAIL PROTECTED] > > > -----Original Message----- > > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, 20 September 2000 22:34 > > To: [EMAIL PROTECTED] > > Subject: Re: Additional behavior for Javac > > > > > > >>>>> "JAF" == Jose Alberto Fernandez > <[EMAIL PROTECTED]> writes: > > > > JAF> If I understand correctly, the current Javac's srcdir > and <src> > > JAF> elements define a kind of search path for in which <include> > > JAF> <exclude> options are applied. > > > > This is the "is <src> a Path or a FileSet" question we had > some weeks > > ago. Think we just forgot to come to a conclusion. > > > > It is a bit like asking whether light is a wave or a particle > :-). I think > the src attribute is closer to a path at present. > > I think what Jose Alberto is trying to achieve is very risky. > Even if he can > convince ant to select the right files, the compiler will > still be using the > sourcepath and may pick up other files from the wrong path. >
The problem for me is that <src>s are not quite a path. In a path, you know that you will be getting only one version of each file (the first one in the path), but here you may be finish passing to the compiler two versions, one from each <src> because the includes apply to both. So eventhough I could work around the compiler limitations, I cannot work around <javac>'s limitations. It would be nice if the behaviour of both where the same. Since this may be kind of an expensive operation one may want to have some sort of "checkduplicates" flag for this situation. Jose Alberto
