Yeah, I've been using that changes thing with stxx for years now. I believe it
started with Forrest. Anyways, sure, that would work too, although I'd prefer
even the xml to be automatically generated. What if we went back to having a
commit message template that could be parsed for info like this?
Don
Niall Pemberton wrote:
On 11/30/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote:
And a big thank you for the +1's :) Any more?
Don
+1.
Any chance we can come up with a way to automatically collect the
information that we've started to put in the release notes as well?
The table consisting of SVN revision # and bugzilla (jira?) ticket
number, shown here
http://struts.apache.org/struts-action/userGuide/release-notes-1.2.8.html
. I'm not familiar with Jira to know if they have a field for a VCS
revision #, but in any case maybe your screen scraper can collect this
info somehow.
Maybe jira has something smarter, but I found a maven feature recently
working on Commons Resources - you can specify an "issue" number in
the change log and attribute credit ("due-to") and as long as you have
the issue tracking *format* configured in your project.properties it
will automatically generate a link and "thanks to" text.
This is what it looks like:
http://tinyurl.com/9qjq5
This is what it generates:
http://jakarta.apache.org/commons/resources/changes-report.html
Niall
Hubert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
