After reading your message, got the same error just a minuite ago! ant 1.4 supports path tags within targets while 1.3 seems to complain. You are most likely running ant 1.3 in your ant server and 1.4 on the command line.
-b Jack Donohue <[EMAIL PROTECTED]> writes: > Sorry. I should have added that I'm using: > Window NT > Emacs 21.2.1 > jde-2.2.9beta9.1 > semantic-1.4beta14 > eieio-0.17beta3 > speedbar-0.14beta4 > > > > > -----Original Message----- > From: Jack Donohue [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 02, 2002 9:10 AM > To: JDE Mailing List > Subject: Ant server problem > > > Hi everyone. > > I've found that the 'Ant Server' option works great, with one exception: A > working target with nested path (see below) works using 'Ant script' or when > I run ant from the command-line. But it fails when using the 'Ant Server' > invocation. The target is as follows: > > <target name="prepare" > > <property name="j2se.home" value="c:/jdk1.3.1_02"/> > <property name="wls.home" value="c:/bea/wlserver6.1"/> > > <path id="courts.web.class.path"> > <pathelement location="${j2se.home}/lib/tools.jar"/> > <pathelement location="${wls.home}/lib/weblogic.jar"/> > <pathelement location="${wls.home}/lib/log4j.jar"/> > <pathelement location="${wls.home}/lib/cos.jar"/> > <pathelement location="${wls.home}/lib/tpdfd133ee.jar"/> > </path> > </target> > > > > Here's the error: > > AntServer output: > -Dant.home=c:/java/jakarta-ant-1.4.1 -buildfile > c:/case/web/courts/build.xml -emacs prepare > Buildfile: c:\case\web\courts\build.xml > > prepare: > > BUILD FAILED > > c:\case\web\courts\build.xml:10: Could not create task of type: path. Common > solutions are to use taskdef to declare your task, or, if this is an > optional task, to put the optional.jar in the lib directory of your ant > installation (ANT_HOME). > > Total time: 0 seconds > > > > > A few things I've tried: > 1. Enable "Jde Ant Use Global Classpath" > 2. Added ant.jar and jakarta-ant-1.4.1-optional.jar to "Jde Ant User Jar > Files". (Don't have any of my own optional task jars). > > Neither change had any effect on the error. > > > Has anyone else had this problem? > > Thanks in advance for any help. > > > Jack.
