ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Unable to locate tools.jar
Date Mon, 12 Jan 2004 11:43:36 GMT
You can´t avoid that.

Ant is started via oata.launcher.Launcher. That class uses
for searching for that library. If it isn´t found that message is printed
with a System.out.println() (no logging available on that time).


> -----Original Message-----
> From: Patrick Martin []
> Sent: Monday, January 05, 2004 4:08 PM
> To: 'Ant Users List'
> Subject: Unable to locate tools.jar
> Hi,
> On Windows, when using ant against a JRE (not a JDK), I get 
> the following
> message even in quiet mode:
> Unable to locate tools.jar. Expected to find it in
> <my-jre-path>\lib\tools.jar
> Then the build process continues correctly.
> Is there any way to avoid this message ? I think I don't use 
> anything in
> tools.jar as I don't do any compilation in my build.xml.
> Thanks,
> Patrick
> Confidentiality Notice: The information contained in this 
> e-mail message is
> intended only for the personal and confidential use of the 
> recipient(s)
> named above. If the reader of this message is not the 
> intended recipient or
> an agent responsible for delivering it to the intended 
> recipient, you are
> hereby notified that you have received this document in error 
> and that any
> review, dissemination, distribution, or copying of this 
> message is strictly
> prohibited. If you have received this communication in error, 
> please notify
> us immediately by e-mail, and delete the original message. 
> Message confidentiel : Les informations contenues dans ce message sont
> destinees a un usage personnel et confidentiel du destinataire indique
> ci-dessus. Si le lecteur de ce message n'est pas le 
> destinataire prevu, ou
> n'est pas une personne en charge de le delivrer au 
> destinataire voulu, vous
> etes par la presente informe que vous avez recu ce document 
> par erreur, et
> que tout examen, transmission, distribution ou copie de ce message est
> totalement interdit. Si vous avez recu cette communication 
> par erreur, nous
> vous remercions de bien vouloir nous avertir immediatement 
> par e-mail et de
> detruire le message d'origine.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message