Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of stojcevicht@gmail.com
 designates 209.85.162.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=m1qXLeLjxDqbZSDH/ERcxLrrDXaRc+6ot+mUWixAt5BgTwmpwwCrLHlR46ueobxSCgBKkNlZBQEFIXNvuccUF7vVSn5x4etkMrexhALazFBWwQiQ7Q30Bi4/DX44nNpC83LLZDi91pQLzXrJZzvdhNRYwN1b4H9H0E3pMq+n+0U=
Message-ID: <fc59deef0710020431h36911fbewcc7f1cc49c13469f@mail.gmail.com>
Date: Tue, 2 Oct 2007 07:31:48 -0400
From: "Tomislav Stojcevich" <stojcevicht@gmail.com>
To: continuum-dev@maven.apache.org
Subject: Re: CONTINUUM-310 - customizable email templates
In-Reply-To: <4701EEC1.3070401@venisse.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fc59deef0710010436p1e41dd97u1df37a538f8bb33@mail.gmail.com>
	 <4701A711.8050007@apache.org> <4701EEC1.3070401@venisse.net>

I think it should be re-opened since there still is no way to
completely customize the template itself other than turning on and off
the output and summary.  In my case the turning on the summary wiith
the build output turned off will give me what I want but it is still
too much.  I'd like to be able to customize further, there are only a
couple of things from the summary that I want to see.  We could
continue to add flags to the xml file and if checks within the
template but where does it stop?

And what about internationalization? that would have to be a separate
issue but allowing access to be able to modify the templates directly
would at least let those users that really need to change the language
of the text that is hardcoded in the template to be able to do it
should they need to.

So how about my idea about extracting the templates from the core jar
into the webapp during the webapp build, that way they can be directly
modified?  This at least allows the default templates to be
customizable easily.


Another issue should be opened to provide the functionality that Rahul
is suggesting about allowing different templates per group or project.
 That would involve more changes.  There would have to be a place in
the database to store template location per project or group or
possibly store the template itself and provide a template edit screen.