On Wed, 2004-12-15 at 13:02, Joel wrote:
> James Abley wrote
>
> > On Wed, 2004-12-15 at 11:42, Joel wrote:
> > > > For that last part, I think that you need to look at <depend/>.
> > > > Have a
> > > >
> > > > <depend srcdir="${src}" destdir="${dest}">
> > > >
> > > > <javac/> is not aware of dependencies and inheritance hierarchies.
> > >
> > > Is <javac/> supposed to be able to tell when a particular source file
> > > is newer than its class file?
> > > [..]
>
> > Sorry, I was a bit ambiguous in my first answer.
> >
> > Yes, it can check a .java source file against the corresponding .class
> > file for timestamp or existence differences which point to requiring a
> > compilation, but my understanding is that it doesn't check for a
> > superclass having changed, or any imports. You may get compile failures
> > thrown by javac; for example, if a new abstract method has been
> > introduced by into a superclass; which would alert you to a potential
> > issue. But you may just get a subtle bug in your application.
>
> So, if I touch a source file, that source file, at least, should
> recompile?
>
> --
> Joel Rees <[EMAIL PROTECTED]>
> digitcom, inc. æåäçãããã
> Kobe, Japan +81-78-672-8800
> ** <http://www.ddcom.co.jp> **
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
That's the way it's always worked for me. For the definitive answer, I
guess you can check the source to see how the fileset for the javac
-sourcepath argument is constructed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
