Hi Alexander,
the taskdef defines the class used for a task. Just dropping the class
into the lib folder is not enough.
WOLips (Eclipse) adds the taskdef the ant tasks provided by woproject
automatically for you.
Take a look at the ant task docs:
http://objectstyle.org/woproject/ant/index.html
Lot of good reading: Embed frameworks, compile java classes and so on.
Ulrich
Am 07.11.2003 um 12:36 schrieb Alexander Schneider:
> Ok, after searching the list archives I found a mail from Ulrich
> saying that one needs to define <taskdef> for that.
>
> I added this to my build.xml and now I can install from the command
> line. But I thought this is not neccessary but would only need to drop
> the jar file in ant_home/lib. Where is a central place to define this
> so that all projects will get it automatically?
>
> Cheers
> Alexander
>
> Alexander Schneider schrieb:
>
>> Hi all,
>> sorry for almost spamming that mailing-list with ant-related
>> questions but I am lost:
>> Now that my ant task only runs from the commandline I tried
>> installing the framework from there.
>> After calling "ant install" I get the error message that Ant doesn´t
>> know anything about a target "woframework".
>> So I copied the woproject.jar to ANT_HOME/lib and also added it to
>> the classpath.
>> But it still fails. Also renaming the target to "WOFramework" didn´t
>> help. From inside Eclipse I can install the frameworks just fine but
>> not from the command line. The eogenerator task is the other way
>> around. Argh. :-(
>> This is Win XP, Eclipse 2.1.2, WOLips 1.0.7.29 and Ant 1.6b2 (command
>> line) and Ant 1.54 (command line, Eclipse). (I mean that I tried it
>> with both versions from the command line to exclude any errors due to
>> 1.6b2!)
>> Cheers
>> Alexander
>
This archive was generated by hypermail 2.0.0 : Wed Nov 12 2003 - 16:43:16 EST