You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jamie Bisotti <jb...@gmail.com> on 2005/05/04 15:52:51 UTC
Re: release-based changelog
I'd be interested in this too. Anyone?
On 4/29/05, Doug Douglass <dd...@denverdata.com> wrote:
> A customer of mine would like to know which source files have changed in
> their project for a given release. The maven-changelog-plugin produces a
> time-based report (default 30 days) of every file change, so it contains
> more info than they would like, and could potentially miss changes if we
> haven't produced a release in the time period.
>
> I've been looking at the maven-changes-plugin, but that requires
> manually maintaining a xdocs/changes.xml document which is very
> manual/tedious. It also seems that changes.xml duplicates info from the
> issue tracking system.
>
> Does anyone know of a way to generate such a release-based report?
>
> TIA,
> Doug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Jamie Bisotti
Software Engineer
Lexmark International, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release-based changelog
Posted by Arik Kfir <ar...@gmail.com>.
+1...
actually, make that +10!
Jamie Bisotti wrote:
>I'd be interested in this too. Anyone?
>
>
>On 4/29/05, Doug Douglass <dd...@denverdata.com> wrote:
>
>
>>A customer of mine would like to know which source files have changed in
>>their project for a given release. The maven-changelog-plugin produces a
>>time-based report (default 30 days) of every file change, so it contains
>>more info than they would like, and could potentially miss changes if we
>>haven't produced a release in the time period.
>>
>>I've been looking at the maven-changes-plugin, but that requires
>>manually maintaining a xdocs/changes.xml document which is very
>>manual/tedious. It also seems that changes.xml duplicates info from the
>>issue tracking system.
>>
>>Does anyone know of a way to generate such a release-based report?
>>
>>TIA,
>>Doug
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>
>
>