better format for changes log?

[Will Glass-Husain <wg...@forio.com>]

Hi,

The Velocity changelog is really a bit of a mess. It's out of date and confusingly formatted.
http://jakarta.apache.org/velocity/docs/changes.html

I'm trying to find a way to make this easier to keep current.  I could just hand-enter each JIRA issue as it's solved.  But I notice that a lot of the Jakarta projects use a common format, with special icons and an RSS feed.  Is this a maven technique?  For example.
http://jakarta.apache.org/turbine/turbine/development/turbine-2.3/changes-report.html

Any suggestions?  Particularly from Henning - I'm curious how you do this with Turbine.

WILL

Re: better format for changes log?

["Henning P. Schmiedehausen" <hp...@intermeta.de>]

"Will Glass-Husain" <wg...@forio.com> writes:

>Any suggestions?  Particularly from Henning - I'm curious how you do =
>this with Turbine.

Use the maven changes format. I started this with my last few commits.

You can find docs at http://mojo.codehaus.org/changes-maven-plugin/

The maven 2.0 version of the plugin can actually parse the JIRA changelog.
Else you simply use the format described on the howto page.

	Best regards
		Henning




-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

		      4 - 8 - 15 - 16 - 23 - 42

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org