Oh! I get it ;-) If "Constants" has a "public static final int VALUE = 1234;" used in other sources, Javac doesn't do an access to Constants.VALUE in the bytecode of other classes using VALUE, but uses 1234 directly instead. So <depend> which only looks at the bytecode would not see the dependency to "Constants"... It would have to look at the source code as well, and thus become a compiler itself...
I'd go with <uptodate> or jikes myself ;-) Thanks for the reference to <depend>! --DD -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 9:46 AM To: [EMAIL PROTECTED] Subject: Re: problem with file dependencies On Wed, 24 Apr 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote: > What could be done is force a rebuild when the constant class (or > source) is newer than any of the other classes (or the corresponding > JARs) (or sources), by wiping out ${build}. Add an <uptodate> > condition should do. If the "constants" are object references and not primitives, <depend> will be the way to go. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
