Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
From: "Mani G. Iyer" <iyer@rcn.com>
To: "'Ant Users List'" <user@ant.apache.org>
Subject: RE: javac and dependent classes
Date: Sun, 20 Jun 2004 12:28:18 -0400
Message-ID: <000001c456e3$981f2780$6401a8c0@u14917.ecpm.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <40D5B40C.3000407@pontarelli.com>
Importance: Normal

Thank you Brian and Neta. 

The depend=true setting in my javac setting did the trick for me.  But I
think I will use javamake to avoid the case Brian mentioned.  

mani

-----Original Message-----
From: Brian Pontarelli [mailto:brian@pontarelli.com] 
Sent: Sunday, June 20, 2004 11:58 AM
To: Ant Users List
Subject: Re: javac and dependent classes


Javac will handle most simple dependency checks. It will compile things 
in the correct order and handle building all your classes. The problem 
arises when you change the interface of one class, but do not recompile 
all the classes. Here, you need to determine dependencies in order to 
protect against runtime exceptions and errors. If you are talking about 
this case, it sounds like Javamake or depend will work for you. 
Otherwise, if you are just talking about compile order, javac will 
handle all that for you.

- brian


Mani G. Iyer wrote:

>Hello:
>
>In the javac task what is the best way to resolve dependencies? Is
there
>anything I can run to determine the order of the classes to be compiled
>prior to running the javac task?
>
>Thanks
>
>mani
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org