From: David Tolpin (firstname.lastname@example.org)
Date: Wed Apr 23 2003 - 08:08:10 PDT
> Is there a reason why the <taskdef> does not work with a @classpathref
> in this case? @see http://ant.apache.org/manual/CoreTasks/taskdef.html
RenderX has allocated as many human resources as it found feasible at
a particular stage of development to Ant task. XEPTask can be efficiently
used for launching XEP and eliminating startup overhead. It is stable
and documented. It is provided as an optional component and does what
it is intended for for each kind of licenses it is supplied with.
Users willing to improve or modify XEP Task are welcome to license
Developer (including stamped) or Server (including stamped) editions
of the software and obtain the source code. The licenses will
include dedicated e-mail support, patches and fixes are welcome
and credits are given.
The reason behind a particular design of each of XEP components is to provide
stable and usable code within constraints imposed by the development process.
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to email@example.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Wed Apr 23 2003 - 07:58:21 PDT