Use Velocity to generate email

Then I would have to copy toAddress and additionalAddresses to another
collection/array, eg actualAddresses.  I don't think it would be worth it.


On Mon, Jul 14, 2014 at 2:06 PM, David Mason <notifications@github.com>
wrote:

> In zanata-war/src/main/java/org/zanata/email/EmailBuilder.java:
>
> > +                ClasspathResourceLoader.class.getName());
> > +        // this allows unit tests to detect missing context vars:
> > +        ve.setProperty("runtime.references.strict", true);
> > +        ve.init();
> > +        return ve;
> > +    }
> > +
> > +    /**
> > +     * Build message using 'strategy' and send it via Transport to 'toAddress'.
> > +     * @param strategy
> > +     * @throws javax.mail.MessagingException
> > +     * @throws java.io.UnsupportedEncodingException
> > +     */
> > +    public void sendMessage(EmailBuilderStrategy strategy,
> > +            InternetAddress toAddress, String receivedReason)
> > +            throws MessagingException, UnsupportedEncodingException {
>
> How about encoding the need for at least one email in the signature:
>
> public void sendMessage(EmailBuilderStrategy strategy, string receivedReason,
> InternetAddress toAddress, InternetAddress ... additionalAdresses)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zanata/zanata-server/pull/534/files#r14863294>.
>