> -----Original Message-----
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]]
> Sent: 27 May 2002 12:04
> To: Ant Users List
> Subject: Re: Ant 1.5beta1 - javac task - compiling classes it shouldn't
>
> Giles,
>
> javac (the underlying compiler - not the task) will pick up classes you
> have
> not explicitly specified if it requires them to satisfy a dependency in
> the
> code you are compiling or it detects that such classes are out of date.
>
> One thing to try is to move the offending Java classes somewhere out of
> javac's reach. It should then complain about the classes it can no longer
> find and your dependency will be revealed.
Doh! I had inadvertently included a source subdirectory when I only needed one class
from it. The extra classes had dependencies, which had dependencies, etc. This is why
it worked when compiling in my IDE as that was skipping the extraneous classes.
I've corrected my mistake and it is only compiling the expected classes now.
Thanks for the advice, I can now fix the other targets accordingly
>
> Classpaths can be converted to properties in 1.4.1, passed as a property
> and
> then a path constructed in the subbuild. Not pretty but a reasonable
> workaround. Nevertheless using the beta is good :-)
Yeah, I'm a bit of a neatness freak when it comes to my code and build environment, so
the beta is definitely the best solution for me.
--
Giles Paterson
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
