On Thu, 9 Feb 2006, Carlton Brown <[EMAIL PROTECTED]> wrote: > "The class (ClassA) in file (file) is out of date due to > (ClassfileA) but has not been deleted because its source file could > not be determined."
I know this warning message from some historical Java files that use multiple classes in the same source file. This warning is issued when a package private class is out of date that lives in a source file that has a differenet name than its source file. > I have a few issues here... > > 1) The source file is there on disk, it definitely exists And has the same name as the class file (minus extension) and the same case and is located in a proper directory hierarchy matching its package? > 2) How can it determine it is "out of date" if it can't identify the > source file? Are you using the closure attribute? Ant may know that a class your class depends on is out of date. > 3) Is there a way to force it to delete the allegedly out-of-date > file even if its source file "could not be determined" and is there > anything wrong with such an approach? If Ant can't find it, it can't delete it. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
