Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 8063 invoked by uid 500); 6 Apr 2001 16:27:09 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 8049 invoked from network); 6 Apr 2001 16:27:08 -0000 Message-ID: From: "Macey, Ian" To: "'ant-user@jakarta.apache.org'" Subject: RE: Make Dependencies Date: Fri, 6 Apr 2001 17:27:05 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > -----Original Message----- > From: Conor MacNeill [mailto:conor@cortexebusiness.com.au] > If you want to create a dependency between A.class and > b.class which is not > reflected in the source, the you are right, and will > not help you. > I guess you can use uptodate as Diane suggested. I've managed to solve my problem using Diane's suggestion. Here's my initial solution using uptodate: . . . > think it would be rare where you want to set up a compile > dependency where > there is no source relationship between the classes. As you can probably tell from the build.xml, my problem is with a file being used to hold a series of static finals which are used in a number of servlets. Unfortunately such static finals slip past past depends' relying "upon the class references encoded into the class files by the compiler" for well known java-gotcha reasons... Thanks for the help - if anyone knows of a better way to do this in Ant let me know, otherwise I think this a workable solution. Ian ___________________________________________________ CAZENOVE & CO. DISCLAIMER, PLEASE NOTE: This communication is for the attention of the named recipient only and should not be passed on to any other person. Information relating to any company or security, is for information purposes only and should not be interpreted as a solicitation or offer to buy or sell any security. The information on which this communication is based has been obtained from sources we believe to be reliable, but we do not guarantee its accuracy or completeness. All expressions of opinion are subject to change without notice. ___________________________________________________