Hi, >Still, adding this class to the email.jar doesn't affect the end user at >all. They can still use the email classes and jar without having >velocity on the classpath. However, if they choose to use the >VelocityEmail class they will obviously, need velocity.
That's be fine by me. The docs can clearly say (even though it'd be obvious to me) that if you want to send Velocity-templated emails, you need Velocity on your runtime classpath. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
