ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conelly, Luis (GNF, Contractor)" <Luis.Cone...@gnf.com>
Subject RE: using telnet in ant 1.6.1
Date Wed, 05 May 2004 18:25:46 GMT
With ant 1.6.1 you need new libraries... see
http://ant.apache.org/manual/install.html#librarydependencies 

Be aware of comments in 
http://ant.apache.org/manual/OptionalTasks/ftp.html

Regards, 
Luis
-----Original Message-----
From: Artemis Ozten [mailto:aozten@webalg.com]
Sent: Wednesday, May 05, 2004 1:24 PM
To: user@ant.apache.org
Subject: using telnet in ant 1.6.1


 
I have been using ant 1.5.4 and telnet task just fine in MS Windows. I
upgraded to ANT 1.6.1 and my telnet task fails:
 
C:\dev\build\remoteTarget.xml:207: Could not create task or type of typo
 
Ant could not find the task or a class this task relies upon.
 
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
 - You have misspelt 'telnet'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
   and this is not found at the right place in the classpath.
   Fix: check the documentation for dependencies.
   Fix: declare the task.
 - The task is an Ant optional task and optional.jar is absent
   Fix: look for optional.jar in ANT_HOME/lib, download if needed
............................
......................
 
 
I copied optional.jar and netComponents.jar to ANT_HOME/lib but result
did not change. The jars are old as ANT 1.5.4. Would that matter? Or
Should I declare the task too? 
 
Thanks for any insight you may offer,
Artemis
This e-mail may contain confidential, proprietary information on
DealerTrack.com, Inc.  It is intended solely for the name recipient(s)
listed above and should be maintained in strictest confidence.  If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED.  If you
have received this e-mail in error, please immediately notify the sender
at and delete this information from your computer and destroy any
related paper copies.
 
.
 

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